Closed
Bug 1489376
Opened 7 years ago
Closed 7 years ago
Fullscreen events should be dispatched in tree order
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: xidorn, Assigned: xidorn)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Currently, when entering fullscreen, we dispatch the event in tree order, but when exiting fullscreen, we dispatch in the reverse tree order (because it makes more sense that innermost one is the earliest to exit fullscreen).
However, since then the spec has been revised to take multi-process document into account. Since fullscreen events are always synced with flush, their relative order becomes less a problem, and it may be easier to dispatch them in a given order for both directions of fullscreen change.
(I don't think this needs to block shipping unprefixed fullscreen, though.)
Assignee | ||
Updated•7 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•7 years ago
|
||
It seems this would actually make it easier to implement bug 1375319.
Assignee: nobody → xidorn+moz
Blocks: 1375319
Assignee | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment on attachment 9007654 [details]
Bug 1489376 - Dispatch fullscreen events in tree order. r=smaug
Olli Pettay [:smaug] has approved the revision.
Attachment #9007654 -
Flags: review+
Pushed by xquan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6b1be7db8f0f
Dispatch fullscreen events in tree order. r=smaug
Comment 5•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•