Mouse events not guaranteed to fire after pointer events
Categories
(Core :: DOM: Events, defect, P3)
Tracking
()
People
(Reporter: rsnow, Assigned: edgar)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36
Steps to reproduce:
https://jsfiddle.net/snowystinger/ceta7fqo/23/
Follow steps outlined in fiddle.
Actual results:
Text selection starts after clicking Foo and this is the console output.
Foo:
foo pointerup capture
body got pointerup
Bar:
bar pointerup capture
body got pointerup
bar mouseup capture
body got mouseup
Expected results:
Foo:
foo pointerup capture
body got pointerup
body got mouseup
This is what happens in Chrome, there is no text selection and all events are fired.
Bar:
bar pointerup capture
body got pointerup
bar mouseup capture
body got mouseup
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=ec28a490365c49cfd4320648652441e1ad8e779f&tochange=2155af8d88c3bd116305378d7e22b947db339c55
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Edgar, would you have time to take a look at this?
Assignee | ||
Comment 3•4 years ago
|
||
I will take a look after the fission focus work.
Assignee | ||
Comment 4•4 years ago
|
||
It looks like we need to do the hittest again after dispatching pointer event if the target is removed in pointer event handler.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Description
•