Open Bug 1675846 Opened 4 years ago Updated 2 years ago

Mouse events not guaranteed to fire after pointer events

Categories

(Core :: DOM: Events, defect, P3)

Firefox 82
defect

Tracking

()

UNCONFIRMED

People

(Reporter: rsnow, Assigned: edgar)

References

(Blocks 2 open bugs, Regression)

Details

(Keywords: regression)

Attachments

(1 file)

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

Component: Untriaged → DOM: Events
Product: Firefox → Core
Has Regression Range: --- → yes

Edgar, would you have time to take a look at this?

Severity: -- → S3
Flags: needinfo?(echen)
Priority: -- → P3

I will take a look after the fission focus work.

Assignee: nobody → echen
Flags: needinfo?(echen)
Blocks: 822898

It looks like we need to do the hittest again after dispatching pointer event if the target is removed in pointer event handler.

Blocks: 1788981
Blocks: pointerevent
No longer blocks: 822898
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: