W3C home > Mailing lists > Public > www-style@w3.org > April 2013

Re: [css21] What's the used value of left/right when overconstrained in relpos?

From: Sylvain Galineau <galineau@adobe.com>
Date: Mon, 29 Apr 2013 16:29:36 -0700
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>
Message-ID: <CDA44E5A.3325%galineau@adobe.com>

On 4/29/13 3:43 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

>On Mon, Apr 29, 2013 at 2:51 PM, Sylvain Galineau <galineau@adobe.com>
>> Though now I'm wondering if saying gCS() returns the computed value in
>> case is really true. Fwiw css3-box described it thus:
>> "The used values of the above properties, except for any values that
>> are ‘auto’, are calculated from the computed values, evaluating
>> percentages.
>> Then apply one of the following cases: […now follows the constraint
>> steps that do not show up in getComputedStyle()...]"
>> In other words, one could describe what's going on as:
>> does return the used value *before any box model constraint adjustments
>> have
>> been made*.
>> Not sure that clarifies things - it implies an extra stage of
>> for these properties - but it also describes the runtime behavior
>> reasonably
>> well.
>Yeah, that value stage is called "not the used value".  ^_^
>Introducing it, specifically to fix an interop issue in t/r/b/l, seems
>like a ton of overkill.

overflow: overkill;


For CSS2.1 the change that makes most sense to me is to eliminate the bit
values being ignored and make sure the width prose aligns with the height
i.e. it consistently states that the specified steps define the used value.

Then CSSOM's job is to define the interop behavior of gCS(); here this
defining the set of properties for which it'll only resolve relative
and percentages and leave specified absolute lengths alone.

Does that make sense?   

Received on Monday, 29 April 2013 23:30:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:29 UTC