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
 
Jonas Sicking  
View profile  
 More options Nov 13 2012, 5:49 am
Newsgroups: mozilla.dev.platform
From: Jonas Sicking <jo...@sicking.cc>
Date: Tue, 13 Nov 2012 02:48:40 -0800
Local: Tues, Nov 13 2012 5:48 am
Subject: Re: UA string: "Touch" or "Tablet" again
Print | View thread | Show original | Report this message | Find messages by this author

On Mon, Nov 12, 2012 at 7:51 AM, Gervase Markham <g...@mozilla.org> wrote:
> 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.

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.

Touch definitely gets my vote in both mobile and tablet UIs from a
puristic point of view. Not sure if putting it in mobile will cause
breakage by sending "tablet websites" to mobile devices though?

/ Jonas


 
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