W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-values] new editor's draft (and [css3-box])

From: David Hyatt <hyatt@apple.com>
Date: Mon, 19 Jan 2009 16:06:36 -0600
Cc: Alex Mogilevsky <alexmog@microsoft.com>, Håkon Wium Lie <howcome@opera.com>, Christoph Päper <christoph.paeper@crissov.de>, "www-style@w3.org" <www-style@w3.org>
Message-id: <2C2184FA-C6D9-4574-B087-AF6F4F971452@apple.com>
To: robert@ocallahan.org
On Jan 19, 2009, at 3:55 PM, Robert O'Callahan wrote:

> On Tue, Jan 20, 2009 at 9:32 AM, Alex Mogilevsky <alexmog@microsoft.com 
> > wrote:
> However if the site is a photographer's portfolio, the artist will  
> likely want his or her pictures to be rendered at optimal resolution  
> (pixel-to-pixel), and they probably have the originals in enormous  
> resolution so they can provide higher resolution images for high  
> resolution displays (and they can know when to pick high resolution  
> originals, e.g. from media query).
>
> If they're using media queries to pick the image file, then why do  
> they need a device pixel unit? They should just specify a fixed px  
> size for the image in the page, set background-size:100%, and use  
> media queries to pick a 1x, 2x, 3x etc resolution file.
>
> We probably should have a media query value that describes the  
> device-pixel-to-CSS-pixel ratio being used by the user agent, to  
> make that approach work optimally. I think that would be a much  
> better solution for this use case.
>

This is in fact implemented by WebKit.

device-pixel-ratio

dave
(hyatt@apple.com)
Received on Monday, 19 January 2009 22:07:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:15 GMT