Implement pointerrawupdate event
Categories
(Core :: DOM: Events, enhancement, P3)
Tracking
()
People
(Reporter: hsinyi, Assigned: masayuki)
References
(Depends on 1 open bug, Blocks 2 open bugs, )
Details
(Keywords: dev-doc-complete, parity-chrome)
User Story
platform-scheduled:2025-06-30
Attachments
(3 files)
This is for implementing https://w3c.github.io/pointerevents/#the-pointerrawupdate-event
Updated•7 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
| Reporter | ||
Updated•2 years ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
Also requested on Connect: https://connect.mozilla.org/t5/ideas/support-for-pointerrawupdate/idi-p/89299
| Assignee | ||
Comment 2•1 year ago
|
||
This patch just defines the event message, an atom for event listener attribute
and managing whether the window may have a listener.
Depends on D243402
| Assignee | ||
Comment 3•1 year ago
|
||
Depends on D243403
| Assignee | ||
Comment 4•1 year ago
|
||
Depends on D243404
Updated•1 year ago
|
Please take care to avoid the following Chrome bugs with pointerrawupdate which so far have remained unfixed:
https://issues.chromium.org/issues/353249342
https://issues.chromium.org/issues/40817651
https://issues.chromium.org/issues/40683756
Comment 6•1 year ago
|
||
Would it be possible to get a test for https://github.com/w3c/pointerevents/issues/509 in some bug? Maybe a followup
| Assignee | ||
Comment 7•1 year ago
|
||
(In reply to Olli Pettay [:smaug][bugs@pettay.fi] from comment #6)
Would it be possible to get a test for https://github.com/w3c/pointerevents/issues/509 in some bug? Maybe a followup
Filed bug 1965118. I'll work on that once I finished working on current Interop work which should be done by end of June.
Comment 10•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/aae164cff6aa
https://hg.mozilla.org/mozilla-central/rev/5718f7f3067e
https://hg.mozilla.org/mozilla-central/rev/93856bf75c44
Updated•1 year ago
|
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
Backed out for causing mochitest failures @ test_pointerrawupdate_event_count.html
| Assignee | ||
Comment 13•1 year ago
|
||
Hmm, xorig test framework is really unstable for pointer events...
Updated•1 year ago
|
Updated•1 year ago
|
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
Comment 16•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/32ba02fa32ec
https://hg.mozilla.org/mozilla-central/rev/37f6acd499b1
https://hg.mozilla.org/mozilla-central/rev/ccd6d2c97e41
Comment 17•1 year ago
|
||
:masayuki could you consider nominating this for a release note? (Process info)
| Assignee | ||
Comment 18•1 year ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Introducing a new API.
[Affects Firefox for Android]: Yes.
[Suggested wording]: pointerrawupdate event is now supported. The event allows the web apps to handle pointermove immediately. However, this event is fired more frequently than pointermove with another hit test for considering the target. Therefore, even only adding an event listener of pointerrawupdate makes the damage to the performance. So, this is intended to improve apps which cannot handle user input smoothly only with coalesced pointermove events.
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/API/Element/pointerrawupdate_event
Comment 19•1 year ago
|
||
Thanks, added to the Fx140 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx140 release notes.
Updated•1 year ago
|
Comment 20•1 year ago
|
||
FF140 MDN docs work for this done in https://github.com/mdn/content/issues/39614
Updated•1 year ago
|
Updated•11 months ago
|
Description
•