Closed Bug 1438357 Opened 6 years ago Closed 6 years ago

MozDOMPointerLock:Exited is dispatched when DOM is at unstable state

Categories

(Core :: DOM: Core & HTML, defect, P2)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla60
Tracking Flags:
Tracking Status
firefox60 --- fixed

People

(Reporter: smaug, Assigned: smaug)

References

Details

Attachments

(1 file)

fullscreen_exit.diff
1.01 KB, patch
baku
: review+
Details | Diff | Splinter Review 
The chrome only event is used by a framescript to send message to parent.
In bug 1413102 event dispatching needs to call SubtreeRoot, and that isn't
set properly when MozDOMPointerLock:Exited is dispatched.
Just dispatch the event a bit later. The event listener does anyhow async message passing to parent.


https://treeherder.mozilla.org/#/jobs?repo=try&revision=747cfe56e68ad03ca96d491efcb8cff03742c7d3

Tryserver build is with other Shadow DOM changes.
Attachment #8951084 - Flags: review?(mrbkap)
oops, named the patch wrong. Not fullscreen, but pointerlock exit.
Attachment #8951084 - Flags: review?(mrbkap) → review+
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e3e179fc8456
MozDOMPointerLock:Exited is dispatched when DOM is at unstable state, r=baku
Priority: -- → P2
https://hg.mozilla.org/mozilla-central/rev/e3e179fc8456
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox60: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: