- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 29 Apr 2013 15:43:35 -0700
- To: Sylvain Galineau <galineau@adobe.com>
- Cc: www-style list <www-style@w3.org>
On Mon, Apr 29, 2013 at 2:51 PM, Sylvain Galineau <galineau@adobe.com> wrote: > Though now I'm wondering if saying gCS() returns the computed value in this > 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 fix-up > steps that do not show up in getComputedStyle()...]" > > In other words, one could describe what's going on as: getComputedStyle() > 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 computation > 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. ~TJ
Received on Monday, 29 April 2013 22:44:22 UTC