Closed Bug 1167371 Opened 10 years ago Closed 9 years ago

[e10s] nsIProcessScriptLoader.loadProcessScript() scoping causes mozIJSSubScriptLoader.loadSubScript() inconsistencies.

Categories

(Core :: DOM: Content Processes, defect)

Product:
Core
Component:
DOM: Content Processes
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
e10s + ---
firefox41 --- affected

People

(Reporter: ma1, Unassigned)

References

Details

If a script loaded by nsIProcessScriptLoader.loadProcessScript() uses mozIJSSubScriptLoader.loadSubScript(), "globals" (top level var / const) are not shared with subscripts, because "top-level vars go on an object that's below the global in the scope chain" (:billm). That's not consistent with other environments, impacting on reuse and sharing of legacy code, e.g. from JavaScript XPCOM components.
There are work arounds for this, if you really want to fix this go for it, but it probably isn't worth the effort.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.