c0817016d2
The POS uses FastClick to circumvent the 300ms touch delay implemented by browsers before a click event is fired. (Although this has since been removed, probably we can get rid of this in the POS at some point as well [1]). The way FastClick works is simple: immediately fire a synthetic event and block the one fired by the browser 300ms later. Recently, browsers have started to only trust native events to trigger default actions [2][3]. Chrome in particular has started not trusting synthetic events since v53. FastClick provides a solution for this with the needsclick class. It will not interfere with events triggered on elements with this class. [1] https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away [2] https://w3c.github.io/uievents/#trusted-events [3] https://www.chromestatus.com/features/5718803933560832 Fixes #14886 |
||
|---|---|---|
| .. | ||
| description | ||
| img | ||
| lib | ||
| src | ||