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
{{ message }}
This repository has been archived by the owner on Jul 31, 2020. It is now read-only.
Thanks for the link! Yes, both techniques have good use cases:
Feature detection: optimize the content for touch-enabled (or not) displays where the window happens to be open.
screen.touchSupport js introspection: Check the properties of multiple displays, place a window on the one with touch support (e.g. for conference rooms with big non-touch video screens and small touch-enabled controller screens)
I believe the updated explainer addresses the desire to select screens by their properties, including touch support.
Please let me know if the proposal's language could better explicitly describe that goal.
If the use case is determining whether to add touch event handlers to your application, there are existing feature detection techniques that can help.
If the use case is a web application that wants to know which screen to place a window that requires touch, screen.touchSupport could be useful?
The text was updated successfully, but these errors were encountered: