[css-animations] Back to Bikeshed issues, now that I've fixed the minor bug. ^_^

Author: tabatkins

css-animations/Overview.bs

@@ -97,10 +97,10 @@ Animations</h2>
 	animated value.
 
 	The start time of an animation is the time at which the style that defines
-	the animation is resolved. An animation specified by dynamically modifying 
-	the element's style will start when this style is resolved; that may be 
-	immediately in the case of a pseudo style rule such as hover, or may be 
-	when the scripting engine returns control to the browser (in the case of 
+	the animation is resolved. An animation specified by dynamically modifying
+	the element's style will start when this style is resolved; that may be
+	immediately in the case of a pseudo style rule such as hover, or may be
+	when the scripting engine returns control to the browser (in the case of
 	style applied by script).
 
 	An animation applies to an element if its name appears as one of the
@@ -193,10 +193,8 @@ Keyframes</h2>
 	'animation-timing-function', the behavior of which is described below. In addition, keyframe rule
 	declarations qualified with !important are ignored.
 
-	<p class="issue">
-	Need to describe what happens if a property is not present in all keyframes.
-	</p>
-	
+	Issue: Need to describe what happens if a property is not present in all keyframes.
+
 	The @keyframes rule that is used by an animation will be the last one encountered in sorted rules
 	order that matches the name of the animation specified by the 'animation-name' property. It must be
 	noted that @keyframes rules cascade; therefore, an animation may derive keyframes from more than one
@@ -214,7 +212,7 @@ Keyframes</h2>
 		  from {
 		    margin-left: 0px;
 		  }
-		  
+
 		  50% {
 		  	margin-left: 110px;
 		  	opacity: 1;
@@ -234,9 +232,9 @@ Keyframes</h2>
 		At the 1s mark, the slide-right animation will have the same state as if we had defined the 50% rule like this:
 
 		<pre>
-		
+
 		@keyframes slide-right {
-		  
+
 		  50% {
 		  	margin-left: 110px;
 		  	opacity: 0.9;
@@ -247,7 +245,7 @@ Keyframes</h2>
 		  }
 
 		}
-		</pre>		
+		</pre>
 
 	</div>
 
@@ -365,23 +363,23 @@ Timing functions for keyframes</h3>
 <h3 id="animation-name">
 The 'animation-name' property</h3>
 
-	 The 'animation-name' property defines a list of animations that apply. Each name is used to select 
-	 the keyframe at-rule that provides the property values for the animation. If the name does not match 
-	 any keyframe at-rule, there are no properties to be animated and the animation will not execute. 
-	 Furthermore, if the animation name is <code>none</code> then there will be no animation. This can be 
-	 used to override any animations coming from the cascade. If multiple animations are attempting to 
+	 The 'animation-name' property defines a list of animations that apply. Each name is used to select
+	 the keyframe at-rule that provides the property values for the animation. If the name does not match
+	 any keyframe at-rule, there are no properties to be animated and the animation will not execute.
+	 Furthermore, if the animation name is <code>none</code> then there will be no animation. This can be
+	 used to override any animations coming from the cascade. If multiple animations are attempting to
 	 modify the same property, then the animation closest to the end of the list of names wins.
 
-	Each animation listed by name should have a corresponding value for the other animation properties 
-	listed below. If the lists of values for the other animation properties do not have the same length, 
-	the length of the 'animation-name' list determines the number of items in each list examined when 
-	starting animations. The lists are matched up from the first value: excess values at the end are not 
-	used. If one of the other properties doesn't have enough comma-separated values to match the number of 
-	values of 'animation-name', the UA must calculate its used value by repeating the list of values until 
-	there are enough. This truncation or repetition does not affect the computed value. 
+	Each animation listed by name should have a corresponding value for the other animation properties
+	listed below. If the lists of values for the other animation properties do not have the same length,
+	the length of the 'animation-name' list determines the number of items in each list examined when
+	starting animations. The lists are matched up from the first value: excess values at the end are not
+	used. If one of the other properties doesn't have enough comma-separated values to match the number of
+	values of 'animation-name', the UA must calculate its used value by repeating the list of values until
+	there are enough. This truncation or repetition does not affect the computed value.
 
-	Note: This is analogous to the behavior of the ‘background-*’properties, with ‘background-image’ analogous 
-	to 'animation-name'. 
+	Note: This is analogous to the behavior of the ‘background-*’properties, with ‘background-image’ analogous
+	to 'animation-name'.
 
 	<pre class='propdef'>
 	Name: animation-name
@@ -606,9 +604,9 @@ The 'animation-play-state' property</h3>
 			The animation continues to apply to the element with the progress it had made before being paused.
 			When unpaused (set back to ''running''), it restarts from where it left off,
 			as if the "clock" that controls the animation had stopped and started again.
-			
-			If the property is set to ''paused'' during the delay phase of the animation, 
-			the delay clock is also paused and resumes as soon as 'animation-play-state' is set back to ''running''. 
+
+			If the property is set to ''paused'' during the delay phase of the animation,
+			the delay clock is also paused and resumes as soon as 'animation-play-state' is set back to ''running''.
 	</dl>
 
 <h3 id="animation-delay">
@@ -697,16 +695,12 @@ The 'animation-fill-mode' property</h3>
 			but a forwards fill will still apply the values of the ''100%'' keyframe,
 			not whatever values were being applied at the time the animation stopped executing.
 
-			<p class="issue">
-			Why does it ignore the progress made by a non-integer iteration count?
-			</p>
+			Issue: Why does it ignore the progress made by a non-integer iteration count?
 
-			<p class="issue">
-			What happens with ''animation-duration: 0; animation-iteration-count: infinite;''?
+			Issue: What happens with ''animation-duration: 0; animation-iteration-count: infinite;''?
 			The animation is instantaneous,
 			but there is no "last complete iteration".
 			In particular, you can't tell whether to use the 0% or 100% keyframe.
-			</p>
 
 		<dt><dfn>backwards</dfn>
 		<dd>
@@ -784,10 +778,8 @@ Animation Events</h2>
 	Any animation for which both a valid keyframe rule and a non-zero duration are defined will run
 	and generate events; this includes animations with empty keyframe rules.
 
-	<p class="issue">
-	This contradicts the 'animation-delay' section,
+	Issue: This contradicts the 'animation-delay' section,
 	which says that a ''0s'' duration animation still fires events.
-	</p>
 
 	The time the animation has been running is sent with each event generated. This allows the event
 	handler to determine the current iteration of a looping animation or the current position of an