@@ -361,8 +361,15 @@ its associated [=keyframes=] are generated as follows:
361
361
362
362
* The <dfn lt="computed keyframe order">computed order</dfn> of |keyframes|--
363
363
which is the order returned by {{KeyframeEffect/getKeyframes()}}--
364
- is found by performing a stable sort on |keyframes|
365
- by each keyframe’s |keyframe offset|.
364
+ is found by
365
+ shifting |initial keyframe|, |final keyframe|, and
366
+ any keyframes whose offset was specified
367
+ as <<percentage>>, '' @keyframes/from'', or '' @keyframes/to''
368
+ to the front of the list,
369
+ and performing a stable sort on these keyframes
370
+ by their |keyframe offset|s.
371
+
372
+ ISSUE: It might be more natural to leave |final keyframe| at the end.
366
373
367
374
* The <dfn lt="used keyframe order">used order</dfn> of |keyframes|--
368
375
which is the order used to interpolate and compute the actual animation frames--
@@ -372,6 +379,13 @@ its associated [=keyframes=] are generated as follows:
372
379
and ordering them from earliest to latest,
373
380
breaking ties by using the [=computed keyframe order=].
374
381
382
+ Note: Although the [=computed keyframe order=]
383
+ sorts keyframes with <<percentage>> offsets,
384
+ it maintains keyframes specified with a <<timeline-range-name>>
385
+ in their [=specified keyframe order=]--
386
+ after any <<percentage>> keyframes,
387
+ even if these come later in the [=used keyframe order=].
388
+
375
389
<h2 id="animation-definition">
376
390
Declaring Animations</h2>
377
391
0 commit comments