Closed Bug 1771814 Opened 2 years ago Closed 2 years ago

Add ESMification test for importing modules from Extension Framework sandboxes

Categories

(WebExtensions :: General, task, P2)

Product:
WebExtensions
Component:
General
Type:
task

Tracking

(firefox104 fixed)

Status:
RESOLVED FIXED
Milestone:
104 Branch
Tracking Flags:
Tracking Status
firefox104 --- fixed

People

(Reporter: zombie, Assigned: zombie)

References

(Blocks 1 open bug)

Details

(Whiteboard: [addons-jira])

Attachments

(1 file)

Bug 1771814 - Add ESMification test for importing modules from ExtensionAPI sandboxes r=yulia,arai
48 bytes, text/x-phabricator-request
Details | Review

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+.

Blocks: esm-ification
Depends on: 1771678
Whiteboard: [addons-jira]
Assignee: nobody → tomica
Status: NEW → ASSIGNED
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

https://hg.mozilla.org/mozilla-central/rev/ba054c599d6f

Status: ASSIGNED → RESOLVED
Closed: 2 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.

Attachment

General

Creator:
Created:
Updated:
Size: