Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.platform
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion UA string: "Touch" or "Tablet" again
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Gervase Markham  
View profile  
 More options Nov 12 2012, 11:11 am
Newsgroups: mozilla.dev.platform
From: Gervase Markham <g...@mozilla.org>
Date: Mon, 12 Nov 2012 16:12:00 +0000
Subject: Re: UA string: "Touch" or "Tablet" again
Print | View thread | Show original | Report this message | Find messages by this author
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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google