Closed
Bug 1904279
Opened 2 years ago
Closed 2 years ago
Get rid of `dom.w3c_pointer_events.dispatch_click_as_pointer_event` pref once the fix of bug 1675847 is shipped in the release channel
Categories
(Core :: DOM: UI Events & Focus Handling, task)
Core
DOM: UI Events & Focus Handling
Tracking
()
RESOLVED
FIXED
130 Branch
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(1 file)
Currently, it depends on a pref, dom.w3c_pointer_events.dispatch_click_as_pointer_event, whether trused click/auxclick/contextmenu events are fired as MouseEvent or PointerEvent. Therefore, their dispatchers have ugly code to dispatch same event with different event classes. So, once we ship it, we should remove the pref ASAP. (I guess that it's the best timing that immediately before the merge from beta to release.)
| Assignee | ||
Updated•2 years ago
|
Assignee: nobody → masayuki
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•2 years ago
|
||
Keep supporting the pref makes a lot of click, auxclick and contextmenu
event creators complicated (and look messy). So, let's delete it as soon as
possible.
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/3b42bb6f097c
Get rid of `dom.w3c_pointer_events.dispatch_click_as_pointer_event` pref r=smaug,pip-reviewers,search-reviewers,devtools-reviewers,urlbar-reviewers,nchevobbe,dao,jteow,mconley
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox130:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
Updated•4 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•