On 12/11/12 16:07, Dirkjan Ochtman wrote:
A) Use "Touch" to indicate "has a touch-sensitive screen (and is not already
marked 'Mobile')". This would lead to us using it on tablets, Windows 8
machines, and any other desktop PC with a touchscreen. It would not be
removed if a keyboard was _also_ present. This is Microsoft's approach.
If the above is true (Windows RT non-touch interfaces are common) then
this seems like a bad option. I.e. if Mozilla was to adopt a "Touch"
token in the UA, it would seem most ideal to only use it on hardware
that's actually touch-capable.
Sorry, yes, in case it's not obvious, I am _not_ suggesting using
"Touch" on non-touch-capable machines! (And neither does Microsoft, AIUI.)
D) Use neither, like Chrome. UA sniffing is evil. Developers should use the
presence of a touch API to detect touch capability, and use flexible layout
to adapt to whatever screen size the user has. This is Google's approach.
Given all the options listed, this one sounds seriously attractive.
Let the developers use appropriate API's to figure out what kind of
layout is appropriate, instead of having them on confusing UA tokens.
In an ideal world, I'm sure they'd all do that. Question is, will they?
Gerv
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
