- From: Rick Byers <notifications@github.com>
- Date: Thu, 23 Feb 2023 13:45:29 -0800
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 23 February 2023 21:45:41 UTC
FWIW for the last 2 years we've [seen](https://chromestatus.com/metrics/feature/timeline/popularity/1098) 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](https://docs.google.com/document/d/1-ZUtS3knhJP4RbWC74fUZbNp6cbytG6Wen7hewdCtdo/edit#). In particular, it's only necessary for UI which aims to have a good experience on devices where the use 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. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/108#issuecomment-1442471487 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/108/1442471487@github.com>
Received on Thursday, 23 February 2023 21:45:41 UTC