- From: Glenn Adams <glenn@skynav.com>
- Date: Thu, 9 Aug 2012 03:42:43 -0600
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <CACQ=j+cFUgY7B-702aQ852RXFwSqPM0oZJ95qoH3KBbVs_6Oag@mail.gmail.com>
On Thu, Aug 9, 2012 at 1:16 AM, fantasai <fantasai.lists@inkedblade.net>wrote: > The current editor's draft has this paragraph: > > # The computed size of all Grid tracks as returned for the > 'grid-definition-rows' > # and 'grid-definition-columns' properties are normalized to used pixel > values. > # All Grid tracks are included in the computed value reported for > 'grid-definition-rows' > # and 'grid-definition-columns' regardless of how the Grid tracks were > created, > # e.g. implicit tracks may be created by Grid items referencing a Grid > line not > # explicitly defined by a 'grid-definition-rows' or > 'grid-definition-columns' > # property. The computed value includes any used values for named > lines; any > # duplicate names must be removed. User agents may use the repeat > syntax to > # avoid expansive string length due to implicit Grid track creation, > large > # spanning values or high repeat counts specified by the author. > > While the result of getComputedStyle might rely on used values > in certain cases, the "computed value" per CSS terminology cannot > depend on used values, as used values are calculated with the > computed values as input. > > So there are two issues here: > 1. Misuse of terminology needs fixing. (See CSS2.1 section 6.1.) > 2. Do we want these properties' getComputedStyle to return > computed or used values? Note that CSSOM uses the term "resolved value" [1] to refer to what getComputedStyle returns. So question #2 should be: what is the resolved value for these properties? [1] http://dvcs.w3.org/hg/csswg/raw-file/tip/cssom/Overview.html#resolved-values
Received on Thursday, 9 August 2012 09:43:34 UTC