Re: [css3-mediaqueries] DPI in resolution media queries

Opened netmagazine.com today, found yet another article documenting the 
problem: 
http://www.netmagazine.com/features/where-are-our-absolute-css-units
The writer seems to be under the impression that this is a browser bug 
that goes against the spec.

I wonder what exactly is needed to convince you guys that this is a real 
problem that needs a solution (any solution!).

On 15/2/12 18:34, Sylvain Galineau wrote:
> [Lea Verou:]
>> Subject: [css3-mediaqueries] DPI in resolution media queries (was: Re:
>> [CSSWG] Minutes and Resolutions Paris F2F 2012-02-08 Wed AM I:)
>>
>> This basically renders resolution media queries *completely useless*, at
>> least in screen media types, just like inches and cm lengths currently
>> are.
>> With the increasing diversity of devices and their resolutions, this
>> would've been tremendously useful to help maintain a readable, comfortable
>> experience no matter the screen DPI. There is currently *no
>> way* to do that.
>> UAs have shown that it *is* possible to implement this as physical DPI,
>> for example that's what Gecko does.
> Possible being the key word here. If and when the OS can give the UA accurate
> info, then it is possible for every driver/peripheral that tells the OS the
> truth.
>
>> I understand the legacy reasons behind defining the in and cm units with a
>> fixed dpi, but there are no legacy reasons to screw this one up. Yes, it
>> might be more consistent, but what's really the value of being consistent
>> with mistakes?!
> It'd be easier to understand the mistake(s) given use-cases. Or better, links
> to sites that depend on Gecko's behavior as you understand it?
>
>
>
>
> -- 
> Lea Verou (http://lea.verou.me | @LeaVerou)

Received on Thursday, 16 February 2012 20:11:52 UTC