Closed
Bug 1251418
Opened 9 years ago
Closed 9 years ago
Make test_sessionStorageBase.html work in e10s
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla47
People
(Reporter: mrbkap, Assigned: mrbkap)
References
(Blocks 1 open bug)
Details
(Whiteboard: btpp-active)
Attachments
(1 file)
3.50 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
This test is disabled because we're not calling the event handler. I have a fix for it.
Assignee | ||
Comment 1•9 years ago
|
||
The core difference between e10s and non-e10s is that the chrome parent for the window in non-e10s is the nsInProcessTabChildGlobal, whereas in e10s it's the nsWindowRoot. SpecialPowers.addChromeEventListener adds the event listener to the frame message manager's global.
MozSessionStorageChanged is a non-bubble only-chrome event fired on the window. That means that in the target phase in non-e10s, it fires on the nsInProcessTabChildGlobal and in e10s it fires on the nsWindowRoot (as far as I can tell, anyway). We should just use a capturing listener so that we're sure to receive the event.
Attachment #8723802 -
Flags: review?(bugs)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → mrbkap
Comment 2•9 years ago
|
||
Comment on attachment 8723802 [details] [diff] [review]
Patch
Yup, I realized the reason during a run last night, but you were faster :)
(I may want to change "chromeonly" dispatch a bit so that it doesn't lead to this kinds of errors, but that is a different bug.)
Attachment #8723802 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 3•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/fbcaba9e6b76349a6cd504c9762e7ed7e4b36397
Bug 1251418 - Make test_sessionStorageBase.html work in e10s. r=smaug
Updated•9 years ago
|
Whiteboard: btpp-active
Comment 4•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox47:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•