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
Manifest V3 support? scripting.registerContentScripts
#11
Labels
enhancement
New feature or request
Comments
fregante
changed the title
Rewrite for Manifest V3 using Chrome’s new API in 2021?
Rewrite for Manifest V3 using Chrome’s new API?
Dec 13, 2021
This was referenced Dec 13, 2021
Firefox seems to have implemented Chrome’s API for the upcoming MV3 support: https://bugzilla.mozilla.org/show_bug.cgi?id=1736582 This means that:
|
fregante
changed the title
Rewrite for Manifest V3 using Chrome’s new API?
Manifest V3 support? Mar 17, 2022
scripting.registerContentScripts
FindingsComparing:
The APIs behave the same
The APIs behave differently
On background worker resume
ResolutionsChrome
Firefox
In short:
Unresolvable problems
|
Finally: The API is simply not compatible with event pages by design — this is not a polyfill limitation. When the page unloads, the content script is no longer registered. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chrome.scripting.registerContentScripts
is coming in Manifest V3, but it won't be available on Manifest V2Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1054624
Details: https://docs.google.com/document/d/1nRJ6iW-W1MVSpJnQzNrRQFLMsr0RycwsNym06TD5i18/edit
Once the API is finalized I'll have to figure out which way to go:
contentScripts.register
in Chrome, but with this new APIThe text was updated successfully, but these errors were encountered: