[Pointer Event] Fire click events for pointer events

RESOLVED INVALID

Status

()

P3
normal
RESOLVED INVALID
2 years ago
a year ago

People

(Reporter: stone, Assigned: stone)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

2 years ago
There are some discussions in https://github.com/w3c/pointerevents/issues/93. Try to figure out the expected click events firing for chorded button

Updated

2 years ago
Priority: -- → P3

Updated

2 years ago
Blocks: 822898

Comment 1

2 years ago
A status update as best as I can follow:

The previously linked PE spec bug has been closed, and as I understand it the correct behaviour is for the click event to be fully dependent on the LMB and completely independent of any chorded secondary button presses. These clicks can be detected using the new auxclick event (bug 1304044).

Firefox appears to already behave correctly with mouse, except:
* Click handlers are still executed at the document and window level (but not directly on elements inside the body) for secondary button clicks. Chrome has already dropped/never had this compat measure. I can't find a specific bug for removing it from Firefox (other than bug 968265) but there probably should be one.
* At least on Windows, calling preventDefault on middle clicks does not stop the autoscroll menu from appearing. (Opened https://github.com/WICG/auxclick/issues/17 for clarity.)

Otherwise, looking at the two tests provided in the PE spec bug, the current Nightly matches both the Chrome Canary and Edge samples for test 1 and matches the agreed expected behaviour for test 2. So ignoring generic UI Events implementation details, it seems to me that Firefox is already compliant re PE chorded buttons :)

So afaik the only remaining work specific to PE is converting click et al from MouseEvents to PointerEvents as per https://github.com/w3c/pointerevents/issues/100.

Missing anything?
(Assignee)

Updated

a year ago
Assignee: nobody → sshih
(Assignee)

Comment 2

a year ago
As comment 1 addressed, we already behave correctly. Closed this bug.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.