|
29 | 29 |
|
30 | 30 | <h1>CSS Transitions</h1> |
31 | 31 |
|
32 | | - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 26 March 2011</h2> |
| 32 | + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 27 March 2011</h2> |
33 | 33 |
|
34 | 34 | <dl> |
35 | 35 | <dt>This version: |
36 | 36 |
|
37 | | - <dd> <a href="http://www.w3.org/TR/2011/ED-css3-transitions-20110326"> |
| 37 | + <dd> <a href="http://www.w3.org/TR/2011/ED-css3-transitions-20110327"> |
38 | 38 | http://dev.w3.org/csswg/css3-transitions/</a> |
39 | | - <!--http://www.w3.org/TR/2011/WD-css3-transitions-20110326--> |
| 39 | + <!--http://www.w3.org/TR/2011/WD-css3-transitions-20110327--> |
40 | 40 |
|
41 | 41 | <dt>Latest version: |
42 | 42 |
|
@@ -794,13 +794,33 @@ <h2 id=starting><span class=secno>3. </span> Starting of transitions</h2> |
794 | 794 | class=property>transition-timing-function</code></a>’, and ‘<a |
795 | 795 | href="#transition-delay"><code |
796 | 796 | class=property>transition-delay</code></a>’ properties at the time |
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. |
| 797 | + the animatable property would first have its new computed value. |
| 798 | + |
| 799 | + <div class=example> |
| 800 | + <p style="display:none"> Example(s):</p> |
| 801 | + |
| 802 | + <pre>li { transition: background-color linear 1s; background: blue; } |
| 803 | +li:hover { transition-duration: 2s; background-color: green; }</pre> |
| 804 | + |
| 805 | + <p> When a list item with these style rules enters the :hover state, the |
| 806 | + computed ‘<a href="#transition-duration"><code |
| 807 | + class=property>transition-duration</code></a>’ at the time that |
| 808 | + ‘<code class=property>background-color</code>’ would have its |
| 809 | + new value (‘<code class=property>green</code>’) is |
| 810 | + ‘<code class=css>2s</code>’, so the transition from |
| 811 | + ‘<code class=property>blue</code>’ to ‘<code |
| 812 | + class=property>green</code>’ takes 2 seconds. However, when the |
| 813 | + list item leaves the :hover state, the transition from ‘<code |
| 814 | + class=property>green</code>’ to ‘<code |
| 815 | + class=property>blue</code>’ takes 1 second.</p> |
| 816 | + </div> |
| 817 | + |
| 818 | + <p> Since this specification does not define when computed values change, |
| 819 | + and thus what changes to computed values are considered simultaneous, |
| 820 | + authors should be aware that changing any of the transition properties a |
| 821 | + small amount of time after making a change that might transition can |
| 822 | + result in behavior that varies between implementations, since the changes |
| 823 | + might be considered simultaneous in some implementations but not others. |
804 | 824 |
|
805 | 825 | <p class=note>Say something about simulaneity |
806 | 826 |
|
|
0 commit comments