Closed sidvishnoi closed 3 months ago
Name | Link |
---|---|
Latest commit | ea9ee330a8f0c5c7249f0268f78c4c2ecff339f0 |
Latest job logs | Run #9495986026 |
Download | |
Download |
1. Should I get rid of manifest v2 stuff? I tested it works fine in Firefox 110 even.
I would keep them for now. We can probably default to using MV3 (renaming manifestv3.json
to manifest.json
) and keep the old manifest for the moment.
2. Should I show the permission error/prompt on all screens?
i don't think so, since the button will be disabled and we check the permission when the user submits the form.
Should I show the permission error/prompt on all screens?
i don't think so, since the button will be disabled and we check the permission when the user submits the form.
So, content script also won't be injected if current URL isn't doesn't have the permission. We ask for the permission only on connect screen, but if some has connected before, and they update the extension, they won't see that they haven't given the permissions. Also valid in case the permission is removed later (for some reason - like mistake or browsers being more strict in future with privacy considerations, like removing permission after N days).
Context
Closes https://github.com/interledger/web-monetization-extension/issues/23
Changes proposed in this pull request
Changes proposed in this pull request
manifestv3.json
, and modify it as needed for Firefox/Chrome support.hosts
permissions on install (automatically or manually), show an error message that permissions are required, along with a button to request permission. No other part of UI is shown until we've the permissions.document.createElement('script')
, anddocument
isn't defined in MV3 background service workers, which causes a fatal crash.Questions:
--mv2
flag during build.~