W3C home > Mailing lists > Public > www-style@w3.org > May 2011

Re: [css3-images] Is the dppx unit needed?

From: Brad Kemper <brad.kemper@gmail.com>
Date: Tue, 24 May 2011 10:32:58 -0700
Message-Id: <D4C6E618-4BA4-4F63-92F2-69FAB14FE7D6@gmail.com>
Cc: Sylvain Galineau <sylvaing@microsoft.com>, www-style list <www-style@w3.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

On May 24, 2011, at 9:46 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

>> Pretty much. The weak use case was all I could think of. That being, if you want an integer number of image pixels per px (for sharper results), then it would be easier to say '2dppx' or '3dppx' than to multiply by 96 for dpi.
>> In your image() function you have 'snap' to fulfill a similar (perhaps not identical) purpose.
> Basically the same purpose.  "300dpi snap" should resolve into 288dpi,
> so you get an even 3 image pixels per CSS px.

If I am reading it right, the snap is to device pixels, right? So it could be something different when printed to a laser printer. I think that is a good thing, and should be noted. 

PS. You have a note about using a term, "pixel rounding". Perhaps you could say "fractional pixels" there instead. Or "rendering that simulates fractional pixels". 
Received on Tuesday, 24 May 2011 17:33:43 UTC

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