world in content_scripts declaration
#485
Labels
implemented: chrome
Implemented in Chrome
supportive: firefox
Supportive from Firefox
supportive: safari
Supportive from Safari
Comments
hanguokai
added
implemented: chrome
birtles
added a commit
to birchill/10ten-ja-reader
that referenced
this issue
Jan 2, 2024
Fixes #1529. MV3 only allows the values "self", "wasm-unsafe-eval", and "wasm-unsafe-eval" for an extension's `script-src` CSP setting. As a result, we can no longer use inline script to update the main world `window` global in order to enable Google Docs' annotated canvas mode. Instead we use the new `world: 'MAIN'` setting and in Firefox, which doesn't yet support that setting, we use Firefox's X-ray vision object unwrapping. Safari doesn't support Google Docs' annotated canvas due to: https://bugs.webkit.org/show_bug.cgi?id=232781 However, Safari have indicated support for implementing `world: 'MAIN'` in: w3c/webextensions#485
birtles
added a commit
to birchill/10ten-ja-reader
that referenced
this issue
Jan 2, 2024
Fixes #1529. MV3 only allows the values "self", "wasm-unsafe-eval", and "wasm-unsafe-eval" for an extension's `script-src` CSP setting. As a result, we can no longer use inline script to update the main world `window` global in order to enable Google Docs' annotated canvas mode. Instead we use the new `world: 'MAIN'` setting and in Firefox, which doesn't yet support that setting, we use Firefox's X-ray vision object unwrapping. Safari doesn't support Google Docs' annotated canvas due to: https://bugs.webkit.org/show_bug.cgi?id=232781 However, Safari have indicated support for implementing `world: 'MAIN'` in: w3c/webextensions#485
bkzhn
pushed a commit
to bkzhn/10ten-ja-reader
that referenced
this issue
Jan 11, 2024
Fixes birchill#1529. MV3 only allows the values "self", "wasm-unsafe-eval", and "wasm-unsafe-eval" for an extension's `script-src` CSP setting. As a result, we can no longer use inline script to update the main world `window` global in order to enable Google Docs' annotated canvas mode. Instead we use the new `world: 'MAIN'` setting and in Firefox, which doesn't yet support that setting, we use Firefox's X-ray vision object unwrapping. Safari doesn't support Google Docs' annotated canvas due to: https://bugs.webkit.org/show_bug.cgi?id=232781 However, Safari have indicated support for implementing `world: 'MAIN'` in: w3c/webextensions#485
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since Chrome 111, Chrome supports a new key
worldincontent_scriptsin manifest, which value is "ISOLATED"(default) or "MAIN". Thus developers can declare content scripts to run in the main world directly.In the meeting Nov 9, 2023, we also discussed this issue when we were discussing #482 . At the moment, Firefox and Safari support (or will support)
worldinbrowser.scriptingAPI, and they are supportive of theworldkey in manifest.The text was updated successfully, but these errors were encountered: