TouchEvent.targetTouches list saved on touchstart is empty on touchmove
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | affected |
People
(Reporter: ksenia, Unassigned)
References
()
Details
Attachments
(1 file)
|
816 bytes,
text/html
|
Details |
This was initially reported in https://github.com/webcompat/web-bugs/issues/94490 where it's impossible to "navigate" a canvas game by swiping on https://www.starbucks.co.jp/egift_holiday2021/find_gift_santa/
I've attached a reduced test case to replicate the behaviour, it's reproducible in RDM or a Firefox Android device.
The site is saving a reference to event.targetTouches on touchstart and accessing it on touchmove, however in Firefox at that point the list is empty, which causes an error. This is not happening in Chrome.
| Reporter | ||
Comment 1•4 years ago
|
||
I found another example similar to this on https://patrickhlauke.github.io/touch/touchlist-objects/ (on touch the green circle representing targetTouches becomes visible in Chrome, but not in Firefox).
Updated•4 years ago
|
Comment 2•4 years ago
|
||
From the description, seems to meet the definition of S2. Edgar, please downgrade if this should be S3 instead.
Updated•4 years ago
|
Comment 3•3 years ago
|
||
Moving to S3, due to the number of webcompat reports we know about so far, also we think websites could work around it by filtering touches with event's target manually. TouchEvent is legacy, and PointerEvent is encouraged to use. :)
Comment 4•1 year ago
|
||
As far as I can tell we don't know of any current site breakage due to this issue? The original starbucks site seems to be 404.
| Reporter | ||
Comment 5•1 year ago
|
||
Removing webcompat priority for now since there are no site reports anymore.
Updated•1 year ago
|
Updated•1 year ago
|
Description
•