- From: Patrick H. Lauke <notifications@github.com>
- Date: Tue, 02 Mar 2021 01:29:51 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 2 March 2021 09:30:03 UTC
I vaguely remember asking before somewhere, but: philosophically, does it not make sense to expose `TouchEvent` (as an API that the browser understands/supports) regardless of presence of an actual touchscreen? Are there other APIs that are simply not exposed (as if the browser didn't understand them / support them at all) in the absence of certain conditions? And yes, Chrome's selective support for certain properties/calls based on the actual presence of a touchscreen is a hacky workaround to naive "mobile-only" detection that assumed "if there's a touchscreen, then i can just listen to touch events as it's mobile ... no need to use mouse events or keyboard / can just switch the the 'mobile' version of the site / etc" -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/952#issuecomment-788763405
Received on Tuesday, 2 March 2021 09:30:03 UTC