- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Mon, 28 Jun 2010 22:32:03 -0700
- To: David Singer <singer@apple.com>
- CC: "www-style@w3.org" <www-style@w3.org>
On 06/17/2010 01:06 PM, fantasai wrote: > > Ok, here's the new paragraph: > > | For a CSS device, these dimensions are either anchored (i) by > | relating the physical units to their physical measurements, or > | (ii) by relating the pixel unit to the <i>reference pixel</i>. > | For print media and similar high-resolution devices, the anchor > | unit should be one of the standard physical units (inches, > | centimeters, etc). For lower-resolution devices, and devices > | with unusual viewing distances, it is recommended instead that > | the anchor unit be the pixel unit. For such devices it is > | recommended that the pixel unit refer to the whole number of > | device pixels that best approximates the reference pixel. David Singer pointed out that it would help to point out that the new definition means px units might not map to an integer number of device pixels, so I've added the following two notes after this paragraph: | <p class="note"Note that if the anchor unit is the pixel unit, | the physical units might not match their physical measurements. | Alternatively if the anchor unit is a physical unit, the pixel | unit might not map to a whole number of device pixels. | | <p class="note">Note that this definition of the pixel unit and | the physical units differs from previous versions of CSS. In | particular, in previous versions of CSS the pixel unit and the | physical units were not related by a fixed ratio: the physical | units were always tied to their physical measurements while the | pixel unit would vary to most closely match the reference pixel. | (This change was made because too much existing content relies | on the assumption of 96dpi, and breaking that assumption breaks | the content.) ~fantasai
Received on Tuesday, 29 June 2010 16:09:35 UTC