Mercurial > drafts / changeset

     1.1 --- a/css-transitions/Overview.bs	Tue Feb 10 20:51:33 2015 -0500
     1.2 +++ b/css-transitions/Overview.bs	Wed Feb 11 13:10:43 2015 +1100
     1.3 @@ -533,6 +533,13 @@
     1.4          </span>
     1.5        </p>
     1.6  
     1.7 +      <p>
     1.8 +        If an element is no longer in the document,
     1.9 +        implementations must remove transitions on it
    1.10 +        from the <a>running transitions</a> and the
    1.11 +        <a>completed transitions</a>.
    1.12 +      </p>
    1.13 +
    1.14        <div class="note">
    1.15  
    1.16          <p>
    1.17 @@ -564,9 +571,6 @@
    1.18        <p>
    1.19          Various things can cause the computed style of an element to change,
    1.20          or for an element to start or stop having computed style.
    1.21 -        (For the purposes of this specification,
    1.22 -        an element has computed style when it is in the document tree,
    1.23 -        and does not have computed style when it is not in the document tree.)
    1.24          These include
    1.25          insertion and removal of elements from the document tree
    1.26          (which both changes whether those elements have computed styles and
    1.27 @@ -587,6 +591,8 @@
    1.28          However,
    1.29          when an implementation updates the computed style for an element
    1.30          to reflect one of these changes,
    1.31 +        or computes the computed style for an element
    1.32 +        newly added to the document,
    1.33          it must update the computed style for all elements to reflect all
    1.34          of these changes at the same time
    1.35          (or at least it must be undetectable that it was done at a
    1.36 @@ -614,8 +620,9 @@
    1.37          When a <a>style change event</a> occurs,
    1.38          implementations must start transitions based on
    1.39          the computed styles that changed in that event.
    1.40 -        If an element does not have a computed style
    1.41 -        either before or after the style change event,
    1.42 +        If an element is not in the document during that
    1.43 +        style change even or was not in the document during
    1.44 +        the previous style change event,
    1.45          then transitions are not started for that element
    1.46          in that style change event.
    1.47          Otherwise,

     2.1 --- a/css-transitions/Overview.html	Tue Feb 10 20:51:33 2015 -0500
     2.2 +++ b/css-transitions/Overview.html	Wed Feb 11 13:10:43 2015 +1100
     2.3 @@ -917,6 +917,14 @@
     2.4        </p>
     2.5  
     2.6        
     2.7 +   <p>
     2.8 +        If an element is no longer in the document,
     2.9 +        implementations must remove transitions on it
    2.10 +        from the <a data-link-type="dfn" href="#running-transition">running transitions</a> and the
    2.11 +        <a data-link-type="dfn" href="#completed-transition">completed transitions</a>.
    2.12 +      </p>
    2.13 +
    2.14 +      
    2.15     <div class="note" role="note">
    2.16  
    2.17          
    2.18 @@ -954,9 +962,6 @@
    2.19     <p>
    2.20          Various things can cause the computed style of an element to change,
    2.21          or for an element to start or stop having computed style.
    2.22 -        (For the purposes of this specification,
    2.23 -        an element has computed style when it is in the document tree,
    2.24 -        and does not have computed style when it is not in the document tree.)
    2.25          These include
    2.26          insertion and removal of elements from the document tree
    2.27          (which both changes whether those elements have computed styles and
    2.28 @@ -977,6 +982,8 @@
    2.29          However,
    2.30          when an implementation updates the computed style for an element
    2.31          to reflect one of these changes,
    2.32 +        or computes the computed style for an element
    2.33 +        newly added to the document,
    2.34          it must update the computed style for all elements to reflect all
    2.35          of these changes at the same time
    2.36          (or at least it must be undetectable that it was done at a
    2.37 @@ -1006,8 +1013,9 @@
    2.38          When a <a data-link-type="dfn" href="#style-change-event">style change event</a> occurs,
    2.39          implementations must start transitions based on
    2.40          the computed styles that changed in that event.
    2.41 -        If an element does not have a computed style
    2.42 -        either before or after the style change event,
    2.43 +        If an element is not in the document during that
    2.44 +        style change even or was not in the document during
    2.45 +        the previous style change event,
    2.46          then transitions are not started for that element
    2.47          in that style change event.
    2.48          Otherwise,