Re: [w3c/touch-events] Specify what browsers do on non-touch devices (#64)

the problem is "define what 'mobile' means" which is generally a question that belies further sweeping assumptions (small screen, no keyboard/mouse only touch, slow connection).

is it perhaps not sufficient to add a non-normative note that leaves it up to user agents whether they expose the API or not, and for authors to feature-detect rather than rely on its presence (and to have a good hard think first about why they're trying to determine this and if really they should be checking the thing that they're making assumption on - viewport size etc - rather than using "touch" as a proxy)?

(unless i'm misunderstanding the question)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/touch-events/issues/64#issuecomment-730500897