[css-animations-2] Add issue to composite order for CSS animations

Author: birtles

css-animations-2/Overview.bs

@@ -66,7 +66,7 @@ with the additions here into a complete level 2 specification.</p>
 
 ## Owning element ## {#owning-element-section}
 
-The <dfn>owning element</dfn> of a CSS Animation refers to the element or
+The <dfn>owning element</dfn> of an animation refers to the element or
 pseudo-element to which the 'animation-name' property was applied that generated
 the animation.
 
@@ -144,6 +144,12 @@ last) as follows:
 The composite order of CSS Animations <em>without</em> an <a>owning element</a>
 is based on their position in the <a>global animation list</a>.
 
+Issue: This differs from the behavior defined for transitions. We should
+probably sort transitions first, then animation, then use the global animation
+list. The reason being that when developer tools etc. hang on to orphaned
+animations and transitions in order to replay them, they should maintain
+roughly the same composite order.
+
 CSS Animations generated using the markup defined in this specification are
 <em>not</em> added to the <a>global animation list</a> when they are created.
 Instead, these animations are appended to the <a>global animation list</a> at

css-animations-2/Overview.html

@@ -185,7 +185,7 @@ <h2 class="heading settled" data-level="1" id="delta"><span class="secno">1. </s
 with the additions here into a complete level 2 specification.</p>
    <h2 class="heading settled" data-level="2" id="animations"><span class="secno">2. </span><span class="content">Animations</span><a class="self-link" href="#animations"></a></h2>
    <h3 class="heading settled" data-level="2.1" id="owning-element-section"><span class="secno">2.1. </span><span class="content">Owning element</span><a class="self-link" href="#owning-element-section"></a></h3>
-   <p>The <dfn data-dfn-type="dfn" data-noexport="" id="owning-element">owning element<a class="self-link" href="#owning-element"></a></dfn> of a CSS Animation refers to the element or
+   <p>The <dfn data-dfn-type="dfn" data-noexport="" id="owning-element">owning element<a class="self-link" href="#owning-element"></a></dfn> of an animation refers to the element or
 pseudo-element to which the <a class="property" data-link-type="propdesc" href="https://drafts.csswg.org/css-animations-1/#propdef-animation-name">animation-name</a> property was applied that generated
 the animation.</p>
    <p>If an animation was generated directly by script (e.g. using
@@ -245,6 +245,11 @@ <h3 class="heading settled" data-level="2.2" id="animation-composite-order"><spa
 element</a>.</p>
    </ol>
    <p>The composite order of CSS Animations <em>without</em> an <a data-link-type="dfn" href="#owning-element">owning element</a> is based on their position in the <a data-link-type="dfn" href="https://w3c.github.io/web-animations/#global-animation-list">global animation list</a>.</p>
+   <p class="issue" id="issue-ea70b453"><a class="self-link" href="#issue-ea70b453"></a> This differs from the behavior defined for transitions. We should
+probably sort transitions first, then animation, then use the global animation
+list. The reason being that when developer tools etc. hang on to orphaned
+animations and transitions in order to replay them, they should maintain
+roughly the same composite order.</p>
    <p>CSS Animations generated using the markup defined in this specification are <em>not</em> added to the <a data-link-type="dfn" href="https://w3c.github.io/web-animations/#global-animation-list">global animation list</a> when they are created.
 Instead, these animations are appended to the <a data-link-type="dfn" href="https://w3c.github.io/web-animations/#global-animation-list">global animation list</a> at
 the first moment when they transition out of the <a data-link-type="dfn" href="https://w3c.github.io/web-animations/#idle-play-state">idle play state</a> after
@@ -817,6 +822,11 @@ <h2 class="no-num heading settled" id="idl-index"><span class="content">IDL Inde
 </pre>
   <h2 class="no-num heading settled" id="issues-index"><span class="content">Issues Index</span><a class="self-link" href="#issues-index"></a></h2>
   <div style="counter-reset:issue">
+   <div class="issue"> This differs from the behavior defined for transitions. We should
+probably sort transitions first, then animation, then use the global animation
+list. The reason being that when developer tools etc. hang on to orphaned
+animations and transitions in order to replay them, they should maintain
+roughly the same composite order.<a href="#issue-ea70b453"> ↵ </a></div>
    <div class="issue"> Create pictures of these examples and verify they make sense.<a href="#issue-69776a9f"> ↵ </a></div>
    <div class="issue"> Define the value of <code>elapsedTime</code> for each case.<a href="#issue-7ee97385"> ↵ </a></div>
    <div class="issue">