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

Re: [CSS2.1][CSSOM] "Used Value" and "auto"

From: Mike Sherov <mike.sherov@gmail.com>
Date: Thu, 12 Jul 2012 11:45:39 -0400
Message-ID: <CAD1Dv_JJDV+8nqE1pdLPV=zZhs=8kroOjZfmyYPQ7vT7mJTixg@mail.gmail.com>
To: Glenn Adams <glenn@skynav.com>
Cc: www-style@w3.org
On Thu, Jul 12, 2012 at 9:29 AM, Glenn Adams <glenn@skynav.com> wrote:

>
> On Thu, Jul 12, 2012 at 2:12 AM, Glenn Adams <glenn@skynav.com> wrote:
>
>> On Thu, Jul 12, 2012 at 12:35 AM, Mike Sherov <mike.sherov@gmail.com>wrote:
>>
>>> The crux of my question is this: is "auto" considered a "used value"? If
>>> not, should it be converted to pixels for top/left/bottom/right (like FF13)?
>>
>>
>> Yes.
>>
>
> Sorry, I meant No, auto (or percentage) is not a used value. If it were
> used (i.e., display is not none), then it is determined or determinable as
> an absolute length, which should be the reported value. However, if display
> is none, then it is indeterminate,  in which case there is no reasonable
> alternative to return the CSS2.1 flavor of the computed value, i.e., 'auto'
> (or percentage), as defined by the Computed value specification of these
> properties, e.g., for top, left, right, bottom:
>
> *Computed value:*  if specified as a length, the corresponding absolute
> length; if specified as a percentage, the specified value; otherwise,
> 'auto'.
>
> So, as pointed out by Boris, these properties do need to be added to the
> CSSOM clause that defines resolved values for width, height, and the like.
>
>
>
> Correct, that is the exact crux of this bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16389 Glad we're all on the
same page :-)


-- 
Mike Sherov
Lead Developer
SNAP Interactive, Inc.
Ticker: STVI.OB
Received on Thursday, 12 July 2012 15:46:31 GMT

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