W3C home > Mailing lists > Public > www-style@w3.org > October 2010

Re: [css-device-adaptation] New draft

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 19 Oct 2010 14:39:49 -0700
Message-ID: <4CBE1025.2030407@jumis.com>
To: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>
CC: Rune Lillesveen <rune@opera.com>, www-style@w3.org, Grace Kloba <klobag@gmail.com>
  Slightly related to all of this,  MS exposes a bunch of information 
via the screen object:

I don't know of cases where DPI is going to drift along one axis at a 
different rate than the other,
but they're exposing that info anyway.

I don't think they've done anything to expose those settings to CSS.

On 10/19/2010 1:50 PM, Kenneth Rohde Christiansen wrote:
> Exactly, but if I do not add a 1.5 scale on a device having 480 pixels 
> in the width, instead of 320, the pages designed with the iphone in 
> mind will have way to small buttons etc. That is why the Android 
> device and Firefox Mobile on the N900 scales every page with viewport 
> meta tags with additional 1.5.
> It is basically a legacy issue, due to the fact that sites *do not* 
> consult the dpi using the media feature. It seems that the 
> targetDensityDpi was added to avoid doing this always on higher dpi 
> devices.
> Kenneth
> On Tue, Oct 19, 2010 at 5:42 PM, Rune Lillesveen <rune@opera.com 
> <mailto:rune@opera.com>> wrote:
>     On Tue, 19 Oct 2010 15:28:36 +0200, Kenneth Rohde Christiansen
>     <kenneth.christiansen@gmail.com
>     <mailto:kenneth.christiansen@gmail.com>> wrote:
>         I think the most important is that you might want to import
>         another css
>         style when the device has a higher dpi, and keep zoom at 1.0.
>     Selecting different css based on device dpi is already supported
>     with the resolution media feature in Media Queries.
>         It is more a legacy thing, as most mobile web app widgets are
>         developed with
>         the iPhone in mind, and they thus become too small on a device
>         with a higher
>         DPI. People have worked around with that by adjusting the zoom
>         factor
>         (multiplying with a dpi factor) and the targetDensityDpi was
>         introduced so
>         that sites could actually make use of the better dpi and
>         ignore the dpi
>         adjustment factor.
>     I don't buy the different-dpi-than-iPhone argument. Content
>     designed for 320x480 iPhones works well on 640x960 iPhones even
>     though the 640x960 iPhones have doubled the dpi. It should of
>     course be noted that "luckily" the CSS pixel is a whole number of
>     device pixels (not 1.5) and the width/height in CSS pixels ends up
>     to be the same on both types of devices, but I'd expect a
>     different width and/or height to be more of a problem for content
>     designed for iPhone than different physical resolution. Unless the
>     CSS pixels aren't scaled to a reasonable amount of physical
>     pixels, which would be a UA issue.
>     -- 
>     Rune Lillesveen
>     Senior Core Developer / Architect
>     Opera Software ASA
> -- 
> Kenneth Rohde Christiansen
> Senior Engineer
> Nokia Danmark A/S
> Phone  +55 81 8895 6002 / E-mail kenneth.christiansen at gmail.com 
> <http://gmail.com>
> http://codeposts.blogspot.com ﹆﹆﹆
Received on Tuesday, 19 October 2010 21:41:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:39 UTC