Closed
Bug 571438
Opened 15 years ago
Closed 15 years ago
MayHavePaintEventListener fails for non-e10s message manager
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mfinkle, Assigned: smaug)
References
Details
Attachments
(1 file)
6.60 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
I am moving the DOM event handlers out of Fennec's chrome front-end and moving them to a content process frame script. I found that MayHavePaintEventListener returns FALSE, even though I have added a "MozAfterPaint" event listener in the frame script.
http://mxr.mozilla.org/mozilla-central/source/layout/base/nsPresContext.cpp#2058
Stepping through in GDB, nsCOMPtr<nsIInProcessContentFrameMessageManager> mm is NULL and none of the other checks trigger, so I get no "MozAfterPaint" event fired.
I then added a simple dummy event listener for "MozAfterPaint" back in the front-end chrome. Then I was able to get the "MozAfterPaint" event fired in the chrome script _and_ in the frame content script.
As I mentioned, this is happening in a mozilla-central, non-e10s message manager build.
Assignee | ||
Comment 1•15 years ago
|
||
I thought I had fixed this, but apparently I forgot to change the fix when
I moved to another event propagation route.
Assignee: nobody → Olli.Pettay
Assignee | ||
Comment 2•15 years ago
|
||
This depends on Bug 568975.
I have manual tests for this in my test-mm.xul.
I'll mochitestify those tests.
Attachment #450637 -
Flags: review?(jst)
Reporter | ||
Comment 3•15 years ago
|
||
(In reply to comment #2)
> Created an attachment (id=450637) [details]
> patch
>
> This depends on Bug 568975.
>
> I have manual tests for this in my test-mm.xul.
> I'll mochitestify those tests.
Depends on: 568975
Reporter | ||
Comment 4•15 years ago
|
||
I meant to say, this bug is breaking the Fennec nightly.
Reporter | ||
Comment 5•15 years ago
|
||
Comment on attachment 450637 [details] [diff] [review]
patch
Just an update: I applied this patch and built Fennec. Works great. MozAfterPaint is being fired.
Updated•15 years ago
|
Attachment #450637 -
Flags: review?(jst) → review+
Assignee | ||
Comment 6•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•15 years ago
|
||
This fix may have regressed MozAfterPaint firing from remote=true web content scripts
Reporter | ||
Comment 8•15 years ago
|
||
Testing on electrolysis branch, local pages work fine (MozAfterPaint is fired) but remote pages do not fire the event in the content script
Assignee | ||
Comment 9•15 years ago
|
||
This fix was for m-c, not for e10s. Seems like the m-c -> e10s merge removed
some code from e10s.
You need to log in
before you can comment on or make changes to this bug.
Description
•