Skip to content

Commit b38ce1e

Browse files
committed
Fix horrible 'at the time of the change' (before or after?) ambiguity in the 'Starting of transitions' text that I wrote a while ago.
1 parent babfffe commit b38ce1e

2 files changed

Lines changed: 15 additions & 12 deletions

File tree

css3-transitions/Overview.html

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -784,22 +784,23 @@ <h3 id=the-transition-shorthand-property-><span class=secno>2.5. </span>
784784

785785
<h2 id=starting><span class=secno>3. </span> Starting of transitions</h2>
786786

787-
<p> When the value of an animatable property changes, implementations must
788-
decide what transitions to start based on the values of the &lsquo;<a
789-
href="#transition-property"><code
787+
<p> When the computed value of an animatable property changes,
788+
implementations must decide what transitions to start based on the values
789+
of the &lsquo;<a href="#transition-property"><code
790790
class=property>transition-property</code></a>&rsquo;, &lsquo;<a
791791
href="#transition-duration"><code
792792
class=property>transition-duration</code></a>&rsquo;, &lsquo;<a
793793
href="#transition-timing-function"><code
794794
class=property>transition-timing-function</code></a>&rsquo;, and &lsquo;<a
795795
href="#transition-delay"><code
796796
class=property>transition-delay</code></a>&rsquo; properties at the time
797-
of the change. Since this specification does not define what property
798-
changes are considered simultaneous, authors should be aware that changing
799-
any of the transition properties a small amount of time after making a
800-
change that might transition can result in behavior that varies between
801-
implementations, since the changes might be considered simultaneous in
802-
some implementations but not others.
797+
the animatable property would first have its new computed value. Since
798+
this specification does not define when computed values change, and thus
799+
what changes to computed values are considered simultaneous, authors
800+
should be aware that changing any of the transition properties a small
801+
amount of time after making a change that might transition can result in
802+
behavior that varies between implementations, since the changes might be
803+
considered simultaneous in some implementations but not others.
803804

804805
<p class=note>Say something about simulaneity
805806

css3-transitions/Overview.src.html

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -738,12 +738,14 @@ <h2 id="starting">
738738
</h2>
739739

740740
<p>
741-
When the value of an animatable property changes,
741+
When the computed value of an animatable property changes,
742742
implementations must decide what transitions to start based on
743743
the values of the 'transition-property', 'transition-duration',
744744
'transition-timing-function', and 'transition-delay' properties
745-
at the time of the change. Since this specification does not
746-
define what property changes are considered simultaneous,
745+
at the time the animatable property would first have its new
746+
computed value. Since this specification does not define
747+
when computed values change, and thus what changes to
748+
computed values are considered simultaneous,
747749
authors should be aware that changing any of the transition
748750
properties a small amount of time after making a change that
749751
might transition can result in behavior that varies between

0 commit comments

Comments
 (0)