Closed
Bug 1799415
Opened 2 years ago
Closed 2 years ago
Support jsm to sys.mjs redirect in content process with sandbox enabled
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
108 Branch
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
It looks like, redirect from the import for jsm to sys.mjs does not work on content process due to sandbox blocks the load for non-existent jsm file,
and fallback path isn't taken.
we should either:
- modify sandbox definition or something to allow .jsm if .sys.jsm exists
- support blocked case in fallback path
2 would be cleaner
|
Assignee | |
Comment 1•2 years ago
|
||
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/128ae8aa1863
Try fallback from jsm to sys.mjs when access is denied by sandbox. r=jonco
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•