[css-animations] Negative delays cause starte event to fire even when play state is paused

Author: Sylvain Galineau

css-animations/Overview.bs

@@ -842,10 +842,11 @@ Types of <code>AnimationEvent</code></h3>
 	<dl dfn-type=event dfn-for=animationevent>
 		<dt><dfn>animationstart</dfn>
 		<dd>
-			The <a idl>animationstart</a> event occurs at the start of the animation. If there is an
-			'animation-delay' then this event will fire once the delay period has expired.
-			A negative delay will cause the event to fire with an elapsedTime equal to the
-			absolute value of the delay.
+			The <a idl>animationstart</a> event occurs at the start of the animation. 
+			If there is an 'animation-delay' then this event will fire once the delay 
+			period has expired. A negative delay will cause the event to fire with 
+			an elapsedTime equal to the absolute value of the delay; in this case the
+			event will fire whether 'animation-play-state' is set to ''running'' or ''paused''.
 			<ul>
 				<li>Bubbles: Yes</li>
 				<li>Cancelable: No</li>
@@ -1061,9 +1062,9 @@ Working Group Resolutions that are pending editing</h2>
     		<li>Agreed that both transitions and animations animate all properties. css-transitions to define animation of non-interoperable/discrete values. They take their starting values below 50% timing function progress, and end values above
     		<li>Dynamic changes to animation properties/keyframes. Tab to propose resolution. (<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14713">Bug 14713</a>)
     		<li>Negative animation-delay values apply against the active duration of the animation i.e. (animation-duration*animation-iteration-count). The delay can thus swallow iterations for which no iteration event will be fired. The start/end events are still fired. Even when delay == (-1*active_duration)
-    		<li>Fire animation start/end events when animation-duration is zero, with 0 elapsedTime
+    		<li><del>Fire animation start/end events when animation-duration is zero, with 0 elapsedTime
     		<li>If animation-iteration-count is infinite and duration is 0, treat the iteration-count as if it was finite and run a 0s second (option A in <a href="http://lists.w3.org/Archives/Public/www-style/2014Sep/0056.html">Brian's mail</a>)
-    		<li>If an animation with a negative animation delay is initially paused, the start event still fires
+    		<li><del>If an animation with a negative animation delay is initially paused, the start event still fires
     		</ul>
 
     	<li>2012-10-29 minutes

css-animations/Overview.html

@@ -864,10 +864,11 @@ <h3 class="heading settled heading" data-level=5.2 id=event-animationevent><span
 	<dl data-dfn-for=animationevent data-dfn-type=event>
 		<dt><dfn class=idl-code data-dfn-for=animationevent data-dfn-type=event data-export="" id=dom-animationevent-animationstart>animationstart<a class=self-link href=#dom-animationevent-animationstart></a></dfn>
 		<dd>
-			The <a data-link-type=idl href=#dom-animationevent-animationstart title=animationstart>animationstart</a> event occurs at the start of the animation. If there is an
-			<a class=property data-link-type=propdesc href=#propdef-animation-delay title=animation-delay>animation-delay</a> then this event will fire once the delay period has expired.
-			A negative delay will cause the event to fire with an elapsedTime equal to the
-			absolute value of the delay.
+			The <a data-link-type=idl href=#dom-animationevent-animationstart title=animationstart>animationstart</a> event occurs at the start of the animation. 
+			If there is an <a class=property data-link-type=propdesc href=#propdef-animation-delay title=animation-delay>animation-delay</a> then this event will fire once the delay 
+			period has expired. A negative delay will cause the event to fire with 
+			an elapsedTime equal to the absolute value of the delay; in this case the
+			event will fire whether <a class=property data-link-type=propdesc href=#propdef-animation-play-state title=animation-play-state>animation-play-state</a> is set to <a class=css data-link-type=maybe href=#valuedef-running title=running>running</a> or <a class=css data-link-type=maybe href=#valuedef-paused title=paused>paused</a>.
 			<ul>
 				<li>Bubbles: Yes</li>
 				<li>Cancelable: No</li>
@@ -1077,10 +1078,10 @@ <h2 class="heading settled heading" data-level=8 id=wg-resolutions-pending><span
     		<li>Agreed that both transitions and animations animate all properties. css-transitions to define animation of non-interoperable/discrete values. They take their starting values below 50% timing function progress, and end values above
     		<li>Dynamic changes to animation properties/keyframes. Tab to propose resolution. (<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14713">Bug 14713</a>)
     		<li>Negative animation-delay values apply against the active duration of the animation i.e. (animation-duration*animation-iteration-count). The delay can thus swallow iterations for which no iteration event will be fired. The start/end events are still fired. Even when delay == (-1*active_duration)
-    		<li>Fire animation start/end events when animation-duration is zero, with 0 elapsedTime
-    		<li>If animation-iteration-count is infinite and duration is 0, treat the iteration-count as if it was finite and run a 0s second (option A in <a href=http://lists.w3.org/Archives/Public/www-style/2014Sep/0056.html>Brian’s mail</a>)
-    		<li>If an animation with a negative animation delay is initially paused, the start event still fires
-    		</ul>
+    		<li><del>Fire animation start/end events when animation-duration is zero, with 0 elapsedTime
+    		</del><li>If animation-iteration-count is infinite and duration is 0, treat the iteration-count as if it was finite and run a 0s second (option A in <a href=http://lists.w3.org/Archives/Public/www-style/2014Sep/0056.html>Brian’s mail</a>)
+    		<li><del>If an animation with a negative animation delay is initially paused, the start event still fires
+    		</del></ul>
 
     	<li>2012-10-29 minutes
 	    	<ul>