Adapt contentScripts/userScripts API to suspendible extension contexts
Categories
(WebExtensions :: General, task, P2)
Tracking
(Not tracked)
People
(Reporter: rpl, Unassigned)
References
(Blocks 1 open bug)
Details
The contentScripts/userScripts API needs at least the following changes:
-
allow to specify an id in the contentScripts/userScripts.register API method, and make the id mandatory for suspendible extension contexts (the id will be needed to make the API able to detect when the suspended page is re-registering the same script once it is waking up)
-
scripts registered from a suspendible extension context should not be destroyed and unregistered automatically when the extension context is being suspended
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Comment 1•2 years ago
|
||
Closing as wontfix:
Bug 1766615 has enabled the scripting API for MV2 extension, and the scripting API has been specifically designed to also cover this since the start and it will also available for MV3 extensions (while the contentScripts and userScripts API namespaces are not available to MV3 extensions) and so the scripting API is also a better path for extensions that will be using the event page in MV2 as part of transitioning to MV3.
Description
•