Closed Bug 1231990 Opened 7 years ago Closed 7 years ago

[e10s] addEventListener("load"...) does not get events in framescript


(Core :: DOM: Content Processes, defect)

44 Branch
Windows 7
Not set



Tracking Status
e10s + ---


(Reporter: dpp23, Unassigned, NeedInfo)



User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:38.0) Gecko/20100101 Firefox/38.1.0 Waterfox/38.1.0
Build ID: 20150607203535

Steps to reproduce:

I have a simple framescript:
addEventListener("load", () => {console.log("LOAD");}, true);

I load it by using
browser.messageManager.loadFrameScript("script.js", false);

On Firefox 44 dev edition, if I have e10s disabled, I get a "load" event for every page load. However if I enable it, I stop getting the events.

I am doing something wrong here or is there an actual bug? I thought framescripts are supposed to behave the same with or without e10s

Actual results:

With e10s I don't get any load events

Expected results:

Getting "load" events with or without e10s
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Could you attach a minimal testcase (.html) showing up the issue, please.
Flags: needinfo?(dpp23)
Hardware: x86_64 → x86
Component: Untriaged → DOM: Events
Product: Firefox → Core
Is it possible that you call browser.messageManager.loadFrameScript("script.js", false); so early that
there isn't the remote browser yet? Could you try what happens if you pass true as the last param?

load events do propagate to TabChildGlobal both in non-e10s and e10s case.
(TabChildGlobal is the JS global object for the frame scripts)
Component: DOM: Events → DMD
Component: DMD → DOM: Content Processes
Blocks: e10s-addons
tracking-e10s: --- → +
re-open if a test case is added
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.