Scan on touch release is incompatible with pointer api #1779
Labels
area/ui-ux
The issue or PR is related to UI/UX/Design
kind/bug
The issue or PR is regarding a bug
regression
This issue or PR is related to a regression
Regression caused by #1585
The
pointerup
event is often hijacked by the browser itself and will not fire. Thepointercancel
event will be triggered if the touch point is moved before the touch is released and there will be nopointerup
event in any case where the browser decides to use the event instead. For example: scrolling, zooming, panning, etc. Essentially any movement of the touch point. This makes it act almost identical toScan on touch tap
.This is easily fixed on pages controlled by whoever desires to receive the
pointerup
and prevent the browser from messing with it by using thetouch-action
css property https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action.But since Yomitan runs on any page a user opens, this is obviously not a solution. Currently, I don't see any way to fix this and restore the old behavior of
Scan on touch release
(without reverting #1585 which is probably undesirable).The text was updated successfully, but these errors were encountered: