As Jim mentioned, we've seen problems with our current browser because, when we turn on touch event interfaces in the browser (i.e. document.createTouchEvent), sites start to assume that this is a touch enabled browser and only a touch enabled browser. i.e. users using a mouse on a touch enabled device suddenly find things stop working.
I think the bigger problem is just that sites/webapps/etc need to design for both mouse and touch control. Having these interfaces available should actually make that easier by providing a way to re-dispatch mouse events as touch if wanted. I worry that including tokens like this just extends this problem and encourages sites to design for a single mode of interaction. If we need to write more examples/blog posts/etc talking about this problem and potential solutions, I'm happy to help. i.e. I agree with Jimm for the most part. IMO, we should set up media queries for touch/mouse/pen/whatever-enabled devices and sites that really want to detect device support (but they shouldn't ever do this!) can use media queried css + window.matchMedia if they really want to do this. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
