- From: David Baron via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 26 Mar 2011 23:06:47 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-transitions
In directory hutz:/tmp/cvs-serv28348
Modified Files:
Overview.html Overview.src.html
Log Message:
Fix horrible 'at the time of the change' (before or after?) ambiguity in the 'Starting of transitions' text that I wrote a while ago.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-transitions/Overview.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- Overview.html 26 Mar 2011 22:53:29 -0000 1.16
+++ Overview.html 26 Mar 2011 23:06:45 -0000 1.17
@@ -784,9 +784,9 @@
<h2 id=starting><span class=secno>3. </span> Starting of transitions</h2>
- <p> When the value of an animatable property changes, implementations must
- decide what transitions to start based on the values of the ‘<a
- href="#transition-property"><code
+ <p> When the computed value of an animatable property changes,
+ implementations must decide what transitions to start based on the values
+ of the ‘<a href="#transition-property"><code
class=property>transition-property</code></a>’, ‘<a
href="#transition-duration"><code
class=property>transition-duration</code></a>’, ‘<a
@@ -794,12 +794,13 @@
class=property>transition-timing-function</code></a>’, and ‘<a
href="#transition-delay"><code
class=property>transition-delay</code></a>’ properties at the time
- of the change. Since this specification does not define what property
- changes are considered simultaneous, authors should be aware that changing
- any of the transition properties a small amount of time after making a
- change that might transition can result in behavior that varies between
- implementations, since the changes might be considered simultaneous in
- some implementations but not others.
+ the animatable property would first have its new computed value. Since
+ this specification does not define when computed values change, and thus
+ what changes to computed values are considered simultaneous, authors
+ should be aware that changing any of the transition properties a small
+ amount of time after making a change that might transition can result in
+ behavior that varies between implementations, since the changes might be
+ considered simultaneous in some implementations but not others.
<p class=note>Say something about simulaneity
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-transitions/Overview.src.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- Overview.src.html 26 Mar 2011 22:53:29 -0000 1.17
+++ Overview.src.html 26 Mar 2011 23:06:45 -0000 1.18
@@ -738,12 +738,14 @@
</h2>
<p>
- When the value of an animatable property changes,
+ When the computed value of an animatable property changes,
implementations must decide what transitions to start based on
the values of the 'transition-property', 'transition-duration',
'transition-timing-function', and 'transition-delay' properties
- at the time of the change. Since this specification does not
- define what property changes are considered simultaneous,
+ at the time the animatable property would first have its new
+ computed value. Since this specification does not define
+ when computed values change, and thus what changes to
+ computed values are considered simultaneous,
authors should be aware that changing any of the transition
properties a small amount of time after making a change that
might transition can result in behavior that varies between
Received on Saturday, 26 March 2011 23:06:49 UTC