element.setPointerCapture should throw NotFoundError if the pointer id is invalid
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: edgar, Assigned: edgar)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed)
Attachments
(2 files)
Per https://w3c.github.io/pointerevents/#setting-pointer-capture, calling the element.setPointerCapture with invalid pointer_id should throw NotFoundError
, right now we throw InvalidPointerId
.
This could fix the WPT failure of pointerevent_setpointercapture_invalid_pointerid.html, https://wpt.fyi/results/pointerevents/pointerevent_setpointercapture_invalid_pointerid.html?label=master&label=experimental&aligned.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Backed out for morchitest failures on test_bug1080361.html
Backout link: https://hg.mozilla.org/integration/autoland/rev/457b43be241b3b6d8b72a9a546830bd0df3a4272
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=314508036&repo=autoland&lineNumber=4822
Please also check failures on pointerevent_releasepointercapture_invalid_pointerid-manual.html -> https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=314508036&repo=autoland&lineNumber=4822
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Now we can pass the wpt one which is no longer a manual test.
Depends on D88859
Assignee | ||
Comment 6•4 years ago
|
||
silly me, there are some tests that need an update as well.
Comment 8•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/225ee73a5a47
https://hg.mozilla.org/mozilla-central/rev/cd2565a9142b
Comment 9•4 years ago
|
||
I'm updating the Binary comat data for this: https://github.com/mdn/browser-compat-data/blob/master/api/Element.json#L8123-L8152
The story for FF desktop is clear, but the FF for Android indicates that this is still stuck behind dom.w3c_pointer_events.enabled
from build 41".
Can you confirm that this is incorrect - ie the most likely assumption is that this is supported all the time from version "59" just like the desktop build.
Last of all, how can I "more generally" check if a core feature is selectively not run on FF for android (so I don't need to ask you this question next time).
Assignee | ||
Comment 10•4 years ago
|
||
The story for FF Android is a bit different, we didn't ship pointer event on FF Android along with FF Desktop from 59.
We shiped it while we move FF Android to GeckoView, see https://bugzilla.mozilla.org/show_bug.cgi?id=1507495. But since it depend on runtime status on FF Android, so we need to update the pref dynamically.
In general, we try to maintain our pref setup in a central place, https://searchfox.org/mozilla-central/source/modules/libpref/init/StaticPrefList.yaml, but pref could be overwrite from other place, too.
Description
•