Closed Bug 1233713 Opened 9 years ago Closed 8 years ago

[e10s] JavaScript-global-constructor only accessible in chrome:// context

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: j, Unassigned)

References

Details

global constructors registered by an add-on with JavaScript-global-constructor are no longer available on websites in firefox nightly.
They can still be used in chrome:// context.

Example extension https://r-w-x.org/jsglobal.git
Bill, this is a known consequence of e10s, right?
Flags: needinfo?(wmccloskey)
I can confirm that the global constructor is still working with e10s disabled.
If memory serves me right, this used to work with e10s enabled.

(If setting browser.tabs.remote.autostart=true enables e10s in 43.0 it works there)
Correct. To make this work in e10s, you would need to load a process script that registers the global in the category manager through JS (rather than in chrome.manifest).
Flags: needinfo?(wmccloskey)
Summary: JavaScript-global-constructor only accessible in chrome:// context → [e10s] JavaScript-global-constructor only accessible in chrome:// context
unless this is showing to break real world add-ons - we're closing as hven't heard more on this
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.