[css-overflow] Stop trying to use "computed style" as a term for all computed values.

Author: dbaron

css-transitions/Overview.bs

@@ -569,39 +569,41 @@ url: http://w3c.github.io/dom/#constructing-events; type: dfn; text: event const
       </div>
 
       <p>
-        Various things can cause the computed style of an element to change,
-        or for an element to start or stop having computed style.
+        Various things can cause the <a>computed values</a> of properties
+        on an element to change.
         These include
         insertion and removal of elements from the document tree
-        (which both changes whether those elements have computed styles and
+        (which both changes whether those elements have <a>computed values</a> and
         can change the styles of other elements through selector matching),
         changes to the document tree that cause
         changes to which selectors match elements,
         changes to style sheets or style attributes,
         and other things.
-        This specification does not define when computed styles are updated,
+        This specification does not define when <a>computed values</a> are updated,
         beyond saying that implementations must not
         use, present, or display something resulting from the CSS
         cascading, value computation, and inheritance process [[!CSS3CASCADE]]
-        without updating the computed style
+        without updating the <a>computed value</a>
         (which means merely that implementations cannot avoid
         meeting requirements of this specification
-        by claiming not to have updated the computed style
+        by claiming not to have updated the <a>computed value</a>
         as part of handling a style change).
         However,
-        when an implementation updates the computed style for an element
+        when an implementation updates the <a>computed value</a> of a
+        property on an element
         to reflect one of these changes,
-        or computes the computed style for an element
+        or computes the <a>computed value</a> of a property on an element
         newly added to the document,
-        it must update the computed style for all elements to reflect all
+        it must update the <a>computed value</a>
+        for all properties and elements to reflect all
         of these changes at the same time
         (or at least it must be undetectable that it was done at a
         different time).
         This processing of a set of simultaneous style changes is called a
         <dfn>style change event</dfn>.
         (Implementations typically have a <a>style change event</a> to
         correspond with their desired screen refresh rate,
-        and when up-to-date computed style is needed
+        and when up-to-date computed style or layout information is needed
         for a script API that depends on it.)
       </p>
 
@@ -619,23 +621,24 @@ url: http://w3c.github.io/dom/#constructing-events; type: dfn; text: event const
       <p>
         When a <a>style change event</a> occurs,
         implementations must start transitions based on
-        the computed styles that changed in that event.
+        the <a>computed values</a> that changed in that event.
         If an element is not in the document during that
         style change even or was not in the document during
         the previous style change event,
         then transitions are not started for that element
         in that style change event.
         Otherwise,
         define the <dfn>before-change style</dfn> as
-        the computed style for the element as of
+        the <a>computed values</a> of all properties on the element as of
         the previous <a>style change event</a>,
         except with any styles derived from declarative
         animations such as CSS Transitions, CSS Animations
         ([[CSS3-ANIMATIONS]]),
         and SMIL Animations ([[SMIL-ANIMATION]], [[SVG11]])
         updated to the current time.
         Likewise, define the <dfn>after-change style</dfn> as
-        the computed style for the element based on the information
+        the <a>computed values</a> of all properties
+        on the element based on the information
         known at the start of that <a>style change event</a>,
         but excluding any styles from CSS Transitions in the computation,
         and inheriting from
@@ -1618,7 +1621,7 @@ dated 19 November 2013</a>:</p>
   <li>The interpolation of ''shadow/inset'' values on shadow lists is no longer backwards.</li>
   <li>A [[#conformance]] section and [[#idl-index]] have been added</li>
   <li>The identifiers accepted by 'transition-property' are defined in terms of <<custom-ident>>.</li>
-  <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>
+  <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>
 </ul>
 
 <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>

css-transitions/Overview.html

@@ -960,39 +960,41 @@ <h2 class="heading settled" data-level="3" id="starting"><span class="secno">3.
 
 
    <p>
-        Various things can cause the computed style of an element to change,
-        or for an element to start or stop having computed style.
+        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
+        on an element to change.
         These include
         insertion and removal of elements from the document tree
-        (which both changes whether those elements have computed styles and
+        (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
         can change the styles of other elements through selector matching),
         changes to the document tree that cause
         changes to which selectors match elements,
         changes to style sheets or style attributes,
         and other things.
-        This specification does not define when computed styles are updated,
+        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,
         beyond saying that implementations must not
         use, present, or display something resulting from the CSS
         cascading, value computation, and inheritance process <a data-link-type="biblio" href="#biblio-css3cascade">[CSS3CASCADE]</a>
-        without updating the computed style
+        without updating the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a>
         (which means merely that implementations cannot avoid
         meeting requirements of this specification
-        by claiming not to have updated the computed style
+        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>
         as part of handling a style change).
         However,
-        when an implementation updates the computed style for an element
+        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
+        property on an element
         to reflect one of these changes,
-        or computes the computed style for an element
+        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
         newly added to the document,
-        it must update the computed style for all elements to reflect all
+        it must update the <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-cascade-3/#computed-value">computed value</a>
+        for all properties and elements to reflect all
         of these changes at the same time
         (or at least it must be undetectable that it was done at a
         different time).
         This processing of a set of simultaneous style changes is called a
         <dfn data-dfn-type="dfn" data-noexport="" id="style-change-event">style change event<a class="self-link" href="#style-change-event"></a></dfn>.
         (Implementations typically have a <a data-link-type="dfn" href="#style-change-event">style change event</a> to
         correspond with their desired screen refresh rate,
-        and when up-to-date computed style is needed
+        and when up-to-date computed style or layout information is needed
         for a script API that depends on it.)
       </p>
 
@@ -1012,23 +1014,24 @@ <h2 class="heading settled" data-level="3" id="starting"><span class="secno">3.
    <p>
         When a <a data-link-type="dfn" href="#style-change-event">style change event</a> occurs,
         implementations must start transitions based on
-        the computed styles that changed in that event.
+        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.
         If an element is not in the document during that
         style change even or was not in the document during
         the previous style change event,
         then transitions are not started for that element
         in that style change event.
         Otherwise,
         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
-        the computed style for the element as of
+        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
         the previous <a data-link-type="dfn" href="#style-change-event">style change event</a>,
         except with any styles derived from declarative
         animations such as CSS Transitions, CSS Animations
         (<a data-link-type="biblio" href="#biblio-css3-animations">[CSS3-ANIMATIONS]</a>),
         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>)
         updated to the current time.
         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
-        the computed style for the element based on the information
+        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 based on the information
         known at the start of that <a data-link-type="dfn" href="#style-change-event">style change event</a>,
         but excluding any styles from CSS Transitions in the computation,
         and inheriting from
@@ -2447,7 +2450,7 @@ <h2 class="heading settled" data-level="9" id="changes"><span class="secno">9. <
 
     <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>.
 
-    <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>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.
 </ul>