W3C home > Mailing lists > Public > www-style@w3.org > February 2012

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

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Wed, 15 Feb 2012 17:00:13 +0000
To: Lea Verou <leaverou@gmail.com>
CC: www-style list <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F01782903428953@TK5EX14MBXC295.redmond.corp.microsoft.com>

[Lea Verou:]
> On 15/2/12 18:34, Sylvain Galineau wrote:
> > 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?
> The mistake is that there is *no way* to define something as X physical
> inches in CSS. Currently, lengths defined in any other unit will end up
> being huge in one screen with huge DPI and tiny in another. Resolution
> media queries were a way to solve this.

OK, sorry for being slow. If the DPI causes the UA to get its inches
completely wrong, how does it get it right with MQs?

> As for sites that depend on (or even use) Gecko's behavior, it's unlikely
> that they exist, since WebKit does not support resolution media queries
> and Presto doesn't support them properly (always assumes a resolution of
> 96dpi). Not sure what Trident does. I'm not saying this change shouldn't
> be done for backwards compatibility reasons. I'm saying it shouldn't be
> done because it makes UAs implement something that authors will likely
> never use like that.
Received on Wednesday, 15 February 2012 17:00:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:12 UTC