Support execution world MAIN in `scripting.executeScript()`
Categories
(WebExtensions :: General, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: willdurand, Unassigned)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
(Whiteboard: [mv3-m2][wecg])
|
||
Updated•3 years ago
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Updated•3 years ago
|
|
||
Updated•2 years ago
|
|
|
Reporter | |
Comment 1•2 years ago
|
||
Unassigned myself because this is not a high priority bug for now.
|
||
Comment 2•2 years ago
|
||
"ISOLATED" was supported in bug 1759932.
This bug is currently about supporting execution in the "MAIN" world (i.e. the web page).
|
|
||
Comment 3•2 years ago
|
||
When we commence work on this, we should also create new bugs or patches to introduce support for world to scripting.registerContentScripts and content_scripts in manifest.json. Chromium implemented that in https://crbug.com/1330986
|
|
||
Comment 4•2 years ago
|
||
The userScripts API proposal at https://github.com/w3c/webextensions/pull/331 includes the "USER_SCRIPT" world, after my feedback to the initial proposal. That is out of scope for this bug, we will file new bugs to implement the USER_SCRIPT world and new APIs when we get there (and these would be part of the userScripts namespace, not the scripting namespace anyway).
When this bug is fixed, we have to adjust the BCD that I added in https://github.com/mdn/browser-compat-data/pull/18878
Description
•