- From: Ryan Cannon <ryan@ryancannon.com>
- Date: Thu, 03 Mar 2005 10:26:41 -0500
- To: Carl Mäsak <cmasak@gmail.com>
- CC: www-style@w3.org
- Message-ID: <42272CB1.3000502@ryancannon.com>
Pixel rounding is actually a phenomenon where browsers, when parsing
relative measurements, are forced to round that width to a certain
pixel. This usually depends on the precision of the browsers
measurements ( i.e.. rounding 10.555px to 11px, 11.6px or 11.56px, or
even mistakenly 10px. Each of these can make a distinct visual
difference, and it varies by browser. Positioniseverything.net has an
excellent example[1].
[1]http://www.positioniseverything.net/round-error.html
This truly is a user agent problem and not a CSS problem, and may
disappear as UAs become more precise. Perhaps CSS 2.1 or 3 should
include a recommendation on how to handle pixel rounding?
Carl Mäsak wrote:
>On Wed, 02 Mar 2005 11:55:59 -0500, Ryan Cannon <ryan@ryancannon.com> wrote:
>
>
>> Some major problems were pixel rounding (which still isn't perfectly
>>fixed),
>>
>>
>
>You might be referring to pixel perfection, in which case it will
>never be "perfectly fixed", as this is not the goal of CSS. Even the
>fact that different user agent manufacturers interpret the CSS specs
>differently, while not a "good" thing, will probably never go away
>completely. The below link points to a fairly sane discussion about
>pixel perfection and designer choices.
>
>http://www.alistapart.com/discuss/flexiblelayouts/7/
>
>
>
--
Ryan Cannon
Instructional Technology
Web Design
RyanCannon.com <http://ryancannon.com/?refer=email>
(989) 463-7060
Received on Thursday, 3 March 2005 15:26:47 UTC