[Pointer Event] button state inconsistency on touch devices
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | verified |
firefox91 | --- | wontfix |
firefox92 | --- | verified |
firefox93 | --- | verified |
People
(Reporter: ray, Assigned: saschanaz)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
RyanVM
:
approval-mozilla-esr91+
|
Details | Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Subscribe to the 'pointerdown' event:
window.addEventListener('pointerdown', (evt => console.info(evt.button, evt.buttons)))
Actual results:
On a touch enabled desktop (Windows), touching the screen results in:
0, 0
While a click gives:
0, 1
Expected results:
I expect 0, 1 in all cases. The current behaviour in FF 91 is inconsistent with:
- FF 90
- The documentation here: https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events#determining_button_states
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Events' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Hi,
Here is the regression range, found using Lenovo Yoga(Windows 10) touchscreen device:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1d7b099453e3b7863650db0d28065571fe320775&tochange=a8c952dcf42810501dbce59333fdd5867e9a1804
Comment 3•3 years ago
|
||
Kagami, would it be possible something caused by bug 1710317? Mind taking a look? Thanks!
Assignee | ||
Comment 4•3 years ago
|
||
Oops, mozregression does point to bug1710317.
Assignee | ||
Comment 5•3 years ago
|
||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Pushed by krosylight@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/217fff940bec Default to eNotPressed in WidgetTouchEvent r=edgar
Comment 7•3 years ago
|
||
Backed out for causing mochitest failures on test_getCoalescedEvents_touch.html.
Backout link: https://hg.mozilla.org/integration/autoland/rev/be3f13e32fe80a8554ab85caebd5f093b069c6f5
Push where failures appeared: https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=amR3GiXtRU-RLGuEzikrFA.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=2b0bb8247bb33438e393ef2c2f4e35dcdc60c093
Failure log: https://treeherder.mozilla.org/logviewer?job_id=349058700&repo=autoland&lineNumber=2941
Backout by mlaza@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/fe930f350465 Backed out changeset 217fff940bec for causing mochitest failures on test_getCoalescedEvents_touch.html. CLOSED TREE
Assignee | ||
Updated•3 years ago
|
Pushed by krosylight@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d1fdf010c95e Default to eNotPressed in WidgetTouchEvent r=edgar
Comment 10•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 11•3 years ago
|
||
The patch landed in nightly and beta is affected.
:saschanaz, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 12•3 years ago
|
||
No known real web compat issue so far, so marking as wontfix.
Hi reporter, if this issue is affecting your website or any web service you are using, please feel free to respond.
Reporter | ||
Comment 13•3 years ago
|
||
This affected a customer using our commercial product; we've responded with a workaround that seems to work for our specific needs, so the impact is manageable.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 14•3 years ago
|
||
Comment on attachment 9237025 [details]
Bug 1725416 - Default to eNotPressed in WidgetTouchEvent r=edgar
Beta/Release Uplift Approval Request
- User impact if declined: Touch behavior on some websites may be broken by this issue, e.g. as reported in comment #13.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This only restores the previous behavior
- String changes made/needed:
Comment 15•3 years ago
|
||
Comment on attachment 9237025 [details]
Bug 1725416 - Default to eNotPressed in WidgetTouchEvent r=edgar
Approved for 92.0b9 and 91.1esr.
Comment 16•3 years ago
|
||
bugherder uplift |
Comment 17•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 18•3 years ago
|
||
Verified - Fixed in latest Nightly 93.0a1 (build id: 20210826213950), Beta 92.0b9 (build id: 20210826192006) and latest 91.1ESR (build id: 20210826130001) using Lenovo Yoga (Windows 10) touchscreen device. Touching the screen results in 0, 1.
Description
•