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
Message from discussion UA string: "Touch" or "Tablet" again

Received: by 10.66.86.100 with SMTP id o4mr812568paz.2.1352894334042;
        Wed, 14 Nov 2012 03:58:54 -0800 (PST)
Path: 6ni80867pbd.1!nntp.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 14 Nov 2012 05:58:53 -0600
Message-ID: <50A3877F.3090406@mozilla.org>
Date: Wed, 14 Nov 2012 11:58:55 +0000
From: Gervase Markham <g...@mozilla.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0a2
MIME-Version: 1.0
Newsgroups: mozilla.dev.platform
To: Kevin Brosnan <kbros...@gmail.com>
Subject: Re: UA string: "Touch" or "Tablet" again
References: <50A11AF7.2000603@mozilla.org> <mailman.2539.1352736488.15607.dev-platform@lists.mozilla.org> <4Ludnbv-AKdSgjzNnZ2dnUVZ_qqdnZ2d@mozilla.org> <mailman.2568.1352741144.15607.dev-platform@lists.mozilla.org>
In-Reply-To: <mailman.2568.1352741144.15607.dev-platform@lists.mozilla.org>
Lines: 13
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 81.187.243.93
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-mahm1Xko1Tuxaes637HR/S1SncmVrmT5oNyzh7YGvO+1k80VQZRJpH88bl/aHmujF+bq+W7iN0pxQtZ!kRrm3fVU8CMHZqvJrYVtRZXwSuuzwpT6Xtv5z/M9iRz2JxOZjCZ2N6V67Fi0Bf+1Jcw=
X-Complaints-To: abuse@mozilla.org
X-DMCA-Complaints-To: ab...@mozilla.org
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 1924
X-Original-Bytes: 1863
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 12/11/12 17:25, Kevin Brosnan wrote:
> On mobile Chrome leaks the device name in the UA this is the current
> method of hardware feature detection on the Android stock browser as
> well.

OK. So given that we don't want to do that (we've rejected it twice 
now), if this is the even-worse alternative, than perhaps we do need to 
provide something in the UA which answers this common "is it supported?" 
question...

Gerv