-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Fix browser specific manifest generation #12533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix browser specific manifest generation #12533
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, great catch!
Hey @MakMuftic, could you update this branch to resolve conflicts? Thanks! |
couldnt modify this pr so i resolved the conflict here #13007 |
Superceded by #13007 |
Fixes: #12532
Explanation:
I tracked a bug inside Metamasks code that creates browser-specific manifests. The idea here is to have
_base.json
manifest that holds manifest properties that are needed on all browsers and then also have browser-specific manifests such aschrome.json
. Then, when manifest for specific browser distribution is created, these two manifests are merged into one. The problem occurs when you have array property such aspermissions
in both_base.json
andchrome.json
(browser-specific manifest). Below you can find examples of how this merge worked before, and how it works now.OLD BEHAVIOUR
NEW BEHAVIOUR
I have read the CLA Document and I hereby sign the CLA