On Tuesday, November 13, 2012 4:49:14 AM UTC-6, Jonas Sicking wrote: > Note that API detection is only possible client-side. (And using > javascript, though this is less of an issue). > > Websites generally send dramatically different content for touch-based > UIs. Different enough that they'd want to send a different piece of > main content. > > Note that putting "touch" in the UA is somewhat different than > traditional UA sniffing. It's actually capability testing which is > what we are encouraging people to do. Using HTTP-headers is the way > you do server-side capability testing, comparable to using JS and > API-detection to do client-side capability testing.
Isn't this what we want to avoid? For the user with a laptop that supports touch they are going to get thrown into touch centric (mobile) interfaces on web sites. I have had this happen on the tablets I test with thanks to the touch interfaces - it's really annoying. Also it seems odd that we would only identify one capability through the UA and not others. By putting "touch" in the UA, what are we conveying exactly? _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
