Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider integrating InputDeviceCapabilities #108

Open
RByers opened this issue Sep 23, 2016 · 1 comment
Open

Consider integrating InputDeviceCapabilities #108

RByers opened this issue Sep 23, 2016 · 1 comment
Labels
UIEvent

Comments

@RByers
Copy link

RByers commented Sep 23, 2016

The sourceCapabilities property of UIEvent was incubated in the WICG. If this API becomes successful (eg. widely used by developers / implemented in more than one browser), then we should consider transitioning it out of incubation and into this spec.
@RByers
Copy link
Author

RByers commented Feb 23, 2023 •
edited
Loading

FWIW for the last 2 years we've seen about 0.6% of page loads in Chrome (i.e. a HUGE number) calling InputDeviceCapabilities#firesTouchEvents. To me, this confirms our hypothesis that the API is addressing a real, but somewhat niche, problem for developers. In particular, it's only necessary for UI which aims to have a good experience on devices where the user commonly uses both a touchscreen and mouse input device. This isn't likely very relevant anywhere WebKit runs, but should potentially be relevant for Gecko on some Windows laptops.

We consider this API successful in chromium and would again be happy to invest in migrating the specification to a WG if there was interest from another implementer.

@RByers RByers mentioned this issue Feb 23, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
UIEvent
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RByers @garykac