mark TimedITem.player and Animatable.getCurrentAnimations at risk

Author: shans

web-animations/index.html

@@ -6587,6 +6587,13 @@ <h3>The <code>TimedItem</code> interface</h3>
               This will be <code>null</code> if this <a>timed
               item</a> is not <a>associated with a player</a>.
             </p>
+	    <p class='issue'>
+	      Feedback has been provided that suggests this reference causes the
+	      relationship between AnimationPlayers and TimedItems to be circular,
+	      which confuses the model. The player attribute should be considered
+	      <strong>at risk</strong> unless a strong use case for the reference
+	      arises.
+	    </p>
           </dd>
           <dt>// Event callbacks</dt><dd></dd>
           <dt>attribute EventHandler onstart</dt>
@@ -7577,6 +7584,15 @@ <h3>The <code>Animatable</code> interface</h3>
               <code>Element</code> are treated as independent <a>Animatable</a>
               objects.
             </p>
+	    <p class="issue">
+	      Feedback has been provided that suggests direct references from
+	      TimedItem objects to AnimationPlayers generate circular reference and 
+	      confuse the model.  Without this reference, getCurrentAnimations is 
+	      not very useful, as the returned TimedItems can't be used to effect
+	      play control. In the absence of a strong use case for a reference from
+	      TimedItem to AnimationPlayer, this feature should be considered
+	      <strong>at risk</strong>.
+	    </p>
           </dd>
           <dt>sequence&lt;AnimationPlayer&gt; getAnimationPlayers()</dt>
           <dd>