Closed
Bug 1771814
Opened 3 years ago
Closed 3 years ago
Add ESMification test for importing modules from Extension Framework sandboxes
Categories
(WebExtensions :: General, task, P2)
WebExtensions
General
Tracking
(firefox104 fixed)
RESOLVED
FIXED
104 Branch
| Tracking | Status | |
|---|---|---|
| firefox104 | --- | fixed |
People
(Reporter: zombie, Assigned: zombie)
References
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
We need to ensure loading global singleton JSMs from inside the api sandbox still works after ESMification switch to ESMs. API scripts need to see the same module instances as all other chrome JSM/ESM code.
Add a test to ensure that the per process singleton behavior is preserved.
Also, add a test that out-of-tree privileged extensions can write code which is able to work during the ESMification transition, across ESR 102 and Firefox 103+.
|
Assignee | |
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
|
Assignee | |
Comment 1•3 years ago
|
||
|
||
Updated•3 years ago
|
Assignee: nobody → tomica
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•3 years ago
|
Severity: -- → N/A
Priority: -- → P2
Pushed by tjovanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ba054c599d6f
Add ESMification test for importing modules from ExtensionAPI sandboxes r=yulia,arai
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox104:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•