Mercurial > drafts / changeset

     1.1 --- a/css-transitions/Overview.bs	Wed Feb 11 13:10:43 2015 +1100
     1.2 +++ b/css-transitions/Overview.bs	Wed Feb 11 13:21:29 2015 +1100
     1.3 @@ -569,31 +569,33 @@
     1.4        </div>
     1.5  
     1.6        <p>
     1.7 -        Various things can cause the computed style of an element to change,
     1.8 -        or for an element to start or stop having computed style.
     1.9 +        Various things can cause the <a>computed values</a> of properties
    1.10 +        on an element to change.
    1.11          These include
    1.12          insertion and removal of elements from the document tree
    1.13 -        (which both changes whether those elements have computed styles and
    1.14 +        (which both changes whether those elements have <a>computed values</a> and
    1.15          can change the styles of other elements through selector matching),
    1.16          changes to the document tree that cause
    1.17          changes to which selectors match elements,
    1.18          changes to style sheets or style attributes,
    1.19          and other things.
    1.20 -        This specification does not define when computed styles are updated,
    1.21 +        This specification does not define when <a>computed values</a> are updated,
    1.22          beyond saying that implementations must not
    1.23          use, present, or display something resulting from the CSS
    1.24          cascading, value computation, and inheritance process [[!CSS3CASCADE]]
    1.25 -        without updating the computed style
    1.26 +        without updating the <a>computed value</a>
    1.27          (which means merely that implementations cannot avoid
    1.28          meeting requirements of this specification
    1.29 -        by claiming not to have updated the computed style
    1.30 +        by claiming not to have updated the <a>computed value</a>
    1.31          as part of handling a style change).
    1.32          However,
    1.33 -        when an implementation updates the computed style for an element
    1.34 +        when an implementation updates the <a>computed value</a> of a
    1.35 +        property on an element
    1.36          to reflect one of these changes,
    1.37 -        or computes the computed style for an element
    1.38 +        or computes the <a>computed value</a> of a property on an element
    1.39          newly added to the document,
    1.40 -        it must update the computed style for all elements to reflect all
    1.41 +        it must update the <a>computed value</a>
    1.42 +        for all properties and elements to reflect all
    1.43          of these changes at the same time
    1.44          (or at least it must be undetectable that it was done at a
    1.45          different time).
    1.46 @@ -601,7 +603,7 @@
    1.47          <dfn>style change event</dfn>.
    1.48          (Implementations typically have a <a>style change event</a> to
    1.49          correspond with their desired screen refresh rate,
    1.50 -        and when up-to-date computed style is needed
    1.51 +        and when up-to-date computed style or layout information is needed
    1.52          for a script API that depends on it.)
    1.53        </p>
    1.54  
    1.55 @@ -619,7 +621,7 @@
    1.56        <p>
    1.57          When a <a>style change event</a> occurs,
    1.58          implementations must start transitions based on
    1.59 -        the computed styles that changed in that event.
    1.60 +        the <a>computed values</a> that changed in that event.
    1.61          If an element is not in the document during that
    1.62          style change even or was not in the document during
    1.63          the previous style change event,
    1.64 @@ -627,7 +629,7 @@
    1.65          in that style change event.
    1.66          Otherwise,
    1.67          define the <dfn>before-change style</dfn> as
    1.68 -        the computed style for the element as of
    1.69 +        the <a>computed values</a> of all properties on the element as of
    1.70          the previous <a>style change event</a>,
    1.71          except with any styles derived from declarative
    1.72          animations such as CSS Transitions, CSS Animations
    1.73 @@ -635,7 +637,8 @@
    1.74          and SMIL Animations ([[SMIL-ANIMATION]], [[SVG11]])
    1.75          updated to the current time.
    1.76          Likewise, define the <dfn>after-change style</dfn> as
    1.77 -        the computed style for the element based on the information
    1.78 +        the <a>computed values</a> of all properties
    1.79 +        on the element based on the information
    1.80          known at the start of that <a>style change event</a>,
    1.81          but excluding any styles from CSS Transitions in the computation,
    1.82          and inheriting from
    1.83 @@ -1618,7 +1621,7 @@
    1.84    <li>The interpolation of ''shadow/inset'' values on shadow lists is no longer backwards.</li>
    1.85    <li>A [[#conformance]] section and [[#idl-index]] have been added</li>
    1.86    <li>The identifiers accepted by 'transition-property' are defined in terms of <<custom-ident>>.</li>
    1.87 -  <li>Define a little bit more about when changes to computed style happen, by saying at least that implementations must not update the effects of computed style without actually updating computed style.</li>
    1.88 +  <li>Define a little bit more about when changes to computed values happen, by saying at least that implementations must not update the effects of computed values without actually updating computed values.</li>
    1.89  </ul>
    1.90  
    1.91  <p>For more details on these changes, see the version control <a href="https://hg.csswg.org/drafts/log/tip/css-transitions/Overview.bs">change log since 2015 January 26</a> and the <a href="https://hg.csswg.org/drafts/log/tip/css-transitions/Overview.src.html">change log from 2013 March 28 to 2015 January 26</a>.</p>

     2.1 --- a/css-transitions/Overview.html	Wed Feb 11 13:10:43 2015 +1100
     2.2 +++ b/css-transitions/Overview.html	Wed Feb 11 13:21:29 2015 +1100
     2.3 @@ -960,31 +960,33 @@
     2.4  
     2.5        
     2.6     <p>
     2.7 -        Various things can cause the computed style of an element to change,
     2.8 -        or for an element to start or stop having computed style.
     2.9 +        Various things can cause the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed values</a> of properties
    2.10 +        on an element to change.
    2.11          These include
    2.12          insertion and removal of elements from the document tree
    2.13 -        (which both changes whether those elements have computed styles and
    2.14 +        (which both changes whether those elements have <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed values</a> and
    2.15          can change the styles of other elements through selector matching),
    2.16          changes to the document tree that cause
    2.17          changes to which selectors match elements,
    2.18          changes to style sheets or style attributes,
    2.19          and other things.
    2.20 -        This specification does not define when computed styles are updated,
    2.21 +        This specification does not define when <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed values</a> are updated,
    2.22          beyond saying that implementations must not
    2.23          use, present, or display something resulting from the CSS
    2.24          cascading, value computation, and inheritance process <a data-link-type="biblio" href="#biblio-css3cascade">[CSS3CASCADE]</a>
    2.25 -        without updating the computed style
    2.26 +        without updating the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a>
    2.27          (which means merely that implementations cannot avoid
    2.28          meeting requirements of this specification
    2.29 -        by claiming not to have updated the computed style
    2.30 +        by claiming not to have updated the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a>
    2.31          as part of handling a style change).
    2.32          However,
    2.33 -        when an implementation updates the computed style for an element
    2.34 +        when an implementation updates the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a> of a
    2.35 +        property on an element
    2.36          to reflect one of these changes,
    2.37 -        or computes the computed style for an element
    2.38 +        or computes the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a> of a property on an element
    2.39          newly added to the document,
    2.40 -        it must update the computed style for all elements to reflect all
    2.41 +        it must update the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a>
    2.42 +        for all properties and elements to reflect all
    2.43          of these changes at the same time
    2.44          (or at least it must be undetectable that it was done at a
    2.45          different time).
    2.46 @@ -992,7 +994,7 @@
    2.47          <dfn data-dfn-type="dfn" data-noexport="" id="style-change-event">style change event<a class="self-link" href="#style-change-event"></a></dfn>.
    2.48          (Implementations typically have a <a data-link-type="dfn" href="#style-change-event">style change event</a> to
    2.49          correspond with their desired screen refresh rate,
    2.50 -        and when up-to-date computed style is needed
    2.51 +        and when up-to-date computed style or layout information is needed
    2.52          for a script API that depends on it.)
    2.53        </p>
    2.54  
    2.55 @@ -1012,7 +1014,7 @@
    2.56     <p>
    2.57          When a <a data-link-type="dfn" href="#style-change-event">style change event</a> occurs,
    2.58          implementations must start transitions based on
    2.59 -        the computed styles that changed in that event.
    2.60 +        the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed values</a> that changed in that event.
    2.61          If an element is not in the document during that
    2.62          style change even or was not in the document during
    2.63          the previous style change event,
    2.64 @@ -1020,7 +1022,7 @@
    2.65          in that style change event.
    2.66          Otherwise,
    2.67          define the <dfn data-dfn-type="dfn" data-noexport="" id="before_change-style">before-change style<a class="self-link" href="#before_change-style"></a></dfn> as
    2.68 -        the computed style for the element as of
    2.69 +        the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed values</a> of all properties on the element as of
    2.70          the previous <a data-link-type="dfn" href="#style-change-event">style change event</a>,
    2.71          except with any styles derived from declarative
    2.72          animations such as CSS Transitions, CSS Animations
    2.73 @@ -1028,7 +1030,8 @@
    2.74          and SMIL Animations (<a data-link-type="biblio" href="#biblio-smil-animation">[SMIL-ANIMATION]</a>, <a data-link-type="biblio" href="#biblio-svg11">[SVG11]</a>)
    2.75          updated to the current time.
    2.76          Likewise, define the <dfn data-dfn-type="dfn" data-noexport="" id="after_change-style">after-change style<a class="self-link" href="#after_change-style"></a></dfn> as
    2.77 -        the computed style for the element based on the information
    2.78 +        the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed values</a> of all properties
    2.79 +        on the element based on the information
    2.80          known at the start of that <a data-link-type="dfn" href="#style-change-event">style change event</a>,
    2.81          but excluding any styles from CSS Transitions in the computation,
    2.82          and inheriting from
    2.83 @@ -2447,7 +2450,7 @@
    2.84    
    2.85      <li>The identifiers accepted by <a class="property" data-link-type="propdesc" href="#propdef-transition-property">transition-property</a> are defined in terms of <a class="production css" data-link-type="type" href="http://dev.w3.org/csswg/css-values-3/#identifier-value">&lt;custom-ident></a>.
    2.86    
    2.87 -    <li>Define a little bit more about when changes to computed style happen, by saying at least that implementations must not update the effects of computed style without actually updating computed style.
    2.88 +    <li>Define a little bit more about when changes to computed values happen, by saying at least that implementations must not update the effects of computed values without actually updating computed values.
    2.89  </ul>
    2.90  
    2.91