You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggests that a property isCoarse boolean is added to allow accurate handling of different pointer-based input devices.
There are a number of benefits that this allows for by allowing to changing the behaviour based on the support for hover for user interaction and better accessibility handling.
The current methods to detect hover support are not always accurate:
Using CSS media queries: The cross-browser support and reliability of those are mixed. A negative query may indicate no support for the query or the current device doesn't support hover.
The PointerEvent.pointerType can help by making assumptions for "mouse" (precise input) and "touch" (coarse input), however "pen" may or may not support hover depending on the type of pen in-use.
Assuming that fireTouchEvents!==true means that the input is precise.
Example scenarios:
Different forms of pen inputs have very different capabilities.
Laptop with mouse and trackpad but coarse input due to accessibility.
The text was updated successfully, but these errors were encountered:
mattrq
changed the title
Suggest adding a firesCoarseEvents property?
Suggest adding a isCoarse property?
Apr 27, 2022
Similar to issue Suggest adding a firesHoverEvents property
Suggests that a property
isCoarse
boolean is added to allow accurate handling of different pointer-based input devices.There are a number of benefits that this allows for by allowing to changing the behaviour based on the support for hover for user interaction and better accessibility handling.
The current methods to detect hover support are not always accurate:
fireTouchEvents!==true
means that the input is precise.Example scenarios:
The text was updated successfully, but these errors were encountered: