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

> It seems `ontouchstart` as a *content attribute* is not defined, and checker.html5.org gives an error for it

Yeah if no spec defines it as a content attribute, then it’s necessary for the checker to report it as an error.

> I propose we mark the APIs historically used for mobile device detection as deprecated:
> - ontouch* members on window, document, Element
> - document.createTouch, document.createTouchList (already deprecated)
> - document.createEvent("TouchEvent")  (not mentioned by the spec at all today)

All sounds good to me. But however it’s done, it’s important we make clear in the spec what the status is of the `ontouch*` content attributes (not just the IDL attributes). If we clearly define the content attributes as obsolete, then I can have the checker emit a specific more-helpful error message for them.

But also to be clear: Note that the HTML spec doesn’t have a “deprecated” category for conformance; instead it only has “obsolete” and “obsolete but conforming”. In terms of the checker behavior, “obsolete” cases cause the checker to emit an error, while “obsolete but conforming” cause the checker to instead emit just a warning.

Anyway, I would be happy to write up a PR for the spec change around this all, once we have agreement on what we want to do here.

-- 
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-331724027