[css-animations] Update pending resolution list

Author: Sylvain Galineau

css-animations/Overview.bs

@@ -1050,7 +1050,7 @@ Working Group Resolutions that are pending editing</h2>
     		<ul>
     		<li>Detail how/when keyframe values are computed; using <a href="http://lists.w3.org/Archives/Public/www-style/2014Aug/0132.html">G.beta in dbaron's mail</a>
     		<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><del>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><del>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><del>Fire animation start/end events when animation-duration is zero, with 0 elapsedTime
     		<li><del>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>)

css-animations/Overview.html

@@ -1065,8 +1065,8 @@ <h2 class="heading settled heading" data-level=8 id=wg-resolutions-pending><span
     		<ul>
     		<li>Detail how/when keyframe values are computed; using <a href=http://lists.w3.org/Archives/Public/www-style/2014Aug/0132.html>G.beta in dbaron’s mail</a>
     		<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><del>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><del>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>)
+    		</del><li><del>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)
     		</del><li><del>Fire animation start/end events when animation-duration is zero, with 0 elapsedTime
     		</del><li><del>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>)
     		</del><li><del>If an animation with a negative animation delay is initially paused, the start event still fires