Tue, 03 Apr 2012 12:09:39 -0700
Copy clearer wording on list repetition from css3-transitions (which was in turn partly taken from css3-background).
css3-animations/Overview.html | file | annotate | diff | comparison | revisions | |
css3-animations/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css3-animations/Overview.html Tue Apr 03 08:58:54 2012 -0700 1.2 +++ b/css3-animations/Overview.html Tue Apr 03 12:09:39 2012 -0700 1.3 @@ -511,11 +511,24 @@ 1.4 cascade. If animations are attempting to modify the same property, then 1.5 the animation closest to the end of the list of names wins. 1.6 1.7 - <p> Each animation listed by name should have a corresponding value for the 1.8 - other animation properties listed below. In the case where the other 1.9 - properties do not have lists of the correct length, their values are 1.10 - repeated to form a list with the same number of entries as <a 1.11 - href="#animation-name"><code class=property>'animation-name'</code></a>. 1.12 + <p id=list-matching> Each animation listed by name should have a 1.13 + corresponding value for the other animation properties listed below. In 1.14 + the case where the lists of values for the other animation properties do 1.15 + not have the same length, the length of the ‘<a 1.16 + href="#animation-name"><code 1.17 + class=property>animation-name</code></a>’ list determines the number 1.18 + of items in each list examined when starting transitions. The lists are 1.19 + matched up from the first value: excess values at the end are not used. If 1.20 + one of the other properties doesn't have enough comma-separated values to 1.21 + match the number of values of ‘<a href="#animation-name"><code 1.22 + class=property>animation-name</code></a>’, the UA must calculate its 1.23 + used value by repeating the list of values until there are enough. This 1.24 + truncation or repetition does not affect the computed value. <span 1.25 + class=note> Note: This is analogous to the behavior of the ‘<code 1.26 + class=css>background-*</code>’ properties, with ‘<code 1.27 + class=property>background-image</code>’ analogous to ‘<a 1.28 + href="#animation-name"><code 1.29 + class=property>animation-name</code></a>’. </span> 1.30 1.31 <table class=propdef> 1.32 <tbody>
2.1 --- a/css3-animations/Overview.src.html Tue Apr 03 08:58:54 2012 -0700 2.2 +++ b/css3-animations/Overview.src.html Tue Apr 03 12:09:39 2012 -0700 2.3 @@ -356,13 +356,26 @@ 2.4 modify the same property, then the animation closest to the end of the 2.5 list of names wins. 2.6 </p> 2.7 - <p> 2.8 + <p id="list-matching"> 2.9 Each animation listed by name should have a corresponding value 2.10 for the other animation properties listed below. In the case where the 2.11 - other properties do not have lists of the correct length, their values 2.12 - are repeated to form a list with the same number of entries as 2.13 - <code class="property">'animation-name'</code>. 2.14 + lists of values for the other animation properties do not have 2.15 + the same length, the length of the 'animation-name' list 2.16 + determines the number of items in each list examined when 2.17 + starting transitions. The lists are matched up from the first 2.18 + value: excess values at the end are not used. If one of the 2.19 + other properties doesn't have enough comma-separated values to 2.20 + match the number of values of 'animation-name', the UA must 2.21 + calculate its used value by repeating the list of values until 2.22 + there are enough. This truncation or repetition does not affect 2.23 + the computed value. 2.24 + <span class="note"> 2.25 + Note: This is analogous to the behavior of the 'background-*' 2.26 + properties, with 'background-image' analogous to 2.27 + 'animation-name'. 2.28 + </span> 2.29 </p> 2.30 + 2.31 <table class="propdef"> 2.32 <tbody> 2.33 <tr>