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

If it's normative and non-ambiguous then it's testable  (e.g. can test that the entire feature set is disabled in the right way) and new implementations (e.g. servo) don't need to reverse engineer other browsers to get web compat.

Disabling support for something can be done in several ways, and if the feature interacts with other features then it becomes unclear what should happen if the spec only has a vauge note about this issue.

As an example, I just fixed the dom spec to throw `NotSupportedError` for createEvent (instead of `TypeError` which it happened to require before without considering that `TouchEvent` could be undefined). This could use a spec hook from the touch events spec to make it clearer.

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