[web-animations-1] Tie most in-text issues to GitHub issues

Author: birtles

web-animations-1/Overview.bs

@@ -576,8 +576,8 @@ is calculated as a fixed offset from the |now| timestamp provided each time the
 This fixed offset is referred to as the document timeline's <dfn>origin
 time</dfn>.
 
-Issue: There must be a better term than &ldquo;origin time&rdquo;&mdash;
-       it's too similar to &ldquo;time origin&rdquo;.
+Issue(2079): There must be a better term than &ldquo;origin time&rdquo;&mdash;
+             it's too similar to &ldquo;time origin&rdquo;.
 
 Prior to establishing the [=time origin=] for its associated document,
 a [=document timeline=] is <a lt="inactive timeline">inactive</a>.
@@ -686,9 +686,10 @@ follows:
 <h4 id="responding-to-a-newly-inactive-timeline">Responding to a newly inactive
   timeline</h4>
 
-Issue: With the set of timelines defined in this level of this specification,
-this situation is not expected to occur. As a result, this section will likely
-be moved to a subsequent level of this specification.
+Issue(2080): With the set of timelines defined in this level of this
+             specification, this situation is not expected to occur. As
+             a result, this section will likely be moved to a subsequent level
+             of this specification.
 
 When the <a>timeline</a> associated with an <a>animation</a>,
 <var>animation</var>, becomes newly <a lt="inactive timeline">inactive</a>,
@@ -1098,11 +1099,11 @@ as CSS Animations [[CSS-ANIMATIONS-1]].
         1.  Set the <a>animation start time</a> of <var>animation</var>
             to <var>new start time</var>.
 
-        Issue(200): If <em>both</em> the <a lt="animation start time">start
-                    time</a> and <a>hold time</a> are specified, we should
-                    probably calculate the <a lt="animation start time">start
-                    time</a> from the <a>hold time</a> instead of using it
-                    as-is.
+        Issue(2073): If <em>both</em> the <a lt="animation start time">start
+                     time</a> and <a>hold time</a> are specified, we should
+                     probably calculate the <a lt="animation start time">start
+                     time</a> from the <a>hold time</a> instead of using it
+                     as-is.
 
     1.  <a lt="resolve a Promise">Resolve</a> <var>animation</var>'s <a>current
         ready promise</a> with <var>animation</var>.
@@ -3384,6 +3385,8 @@ Note: this procedure permits overlapping <a>keyframes</a>.
     href='http://lists.w3.org/Archives/Public/public-fx/2013AprJun/0184.html'>section
     4 (Keyframe offsets outside [0, 1]) of minuted discussion from Tokyo
       2013 F2F</a>.
+
+    <a href="https://github.com/w3c/csswg-drafts/issues/2081">&lt;https://github.com/w3c/csswg-drafts/issues/2081&gt;</a>
 </div>
 
 
@@ -3927,14 +3930,14 @@ apart from the timing model.
 
 </div>
 
-Issue: The <code>remove()</code> method can be used to remove an effect from
-either its parent group or animation. Should we keep it in level 1 and define it
-simply as removing the animation from its animation?
+Issue(2082): The <code>remove()</code> method can be used to remove an effect
+from either its parent group or animation. Should we keep it in level 1 and
+define it simply as removing the animation effect from its animation?
 
 
 <h3 id="the-animationeffecttimingreadonly-interface">The <code>AnimationEffectTimingReadOnly</code> interface</h3>
 
-Issue: This interface needs a constructor.
+Issue(2055): This interface needs a constructor.
 
 <pre class="idl">
 [Exposed=Window]
@@ -4050,7 +4053,7 @@ The {{AnimationEffectTiming}} interface is a mutable subclass of
 {{AnimationEffectTimingReadOnly}} returned for the <code>timing</code> attribute
 of a mutable <a>animation effect</a> such as {{KeyframeEffect}}.
 
-Issue: This interface needs a constructor.
+Issue(2055): This interface needs a constructor.
 
 <pre class='idl'>
 [Exposed=Window]
@@ -4373,8 +4376,8 @@ interface KeyframeEffect : KeyframeEffectReadOnly {
         Attributes must be assigned in the order in which they appear in the
         {{AnimationEffectTimingReadOnly}} interface.
 
-        Issue: Make a constructor for {{AnimationEffectTimingReadOnly}} and call
-        that here.
+        Issue(2055): Make a constructor for {{AnimationEffectTimingReadOnly}}
+                     and call that here.
 
     1.  If <var>options</var> is a {{KeyframeEffectOptions}} object,
         assign the {{KeyframeEffectReadOnly/iterationComposite}}, and
@@ -5562,16 +5565,16 @@ partial interface Document {
     changes to animation such as changes to animation-related style properties
     that have yet to be processed.
 
-    Issue: Both this method and {{Animatable/getAnimations()}} on the
-           {{Animatable}} interface require retaining forwards-filling
-           <a>animation effects</a> and their <a>animations</a>
-           such that a document that
-           repeatedly produces forwards-filling animations will consume memory
-           in an unbounded fashion.
-           We may need to revise this definition (previously these methods
-           only returned animations whose <a>target effect</a> was
-           <a>current</a>) or provide a loophole for implementations to discard
-           old animations in such conditions.
+    Issue(2054): Both this method and {{Animatable/getAnimations()}} on the
+                 {{Animatable}} interface require retaining forwards-filling
+                 <a>animation effects</a> and their <a>animations</a>
+                 such that a document that
+                 repeatedly produces forwards-filling animations will consume
+                 memory in an unbounded fashion.
+                 We may need to revise this definition (previously these methods
+                 only returned animations whose <a>target effect</a> was
+                 <a>current</a>) or provide a loophole for implementations to
+                 discard old animations in such conditions.
 
 </div>
 
@@ -5792,7 +5795,7 @@ Animations content.
 If provided, this behavior SHOULD be achieved by adjusting the <a>time
 values</a> of any <a>timelines</a> that track wallclock time.
 
-Issue: Is this at odds with those <a>time values</a> being relative to
+Issue(2083): Is this at odds with those <a>time values</a> being relative to
     <code>navigationStart</code> and with <code>requestAnimationFrame</code>
     using the same time as <code>document.timeline.currentTime</code>?