Skip to content

Commit d4315ff

Browse files
committed
[css-transitions-2] Define order for sorting transitioncancel events
See #11064.
1 parent b704bfe commit d4315ff

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

css-transitions-2/Overview.bs

+6-1
Original file line numberDiff line numberDiff line change
@@ -363,6 +363,11 @@ are sorted in composite order (first to last) as follows:
363363
such that ‘-moz-column-width’ sorts before
364364
‘column-width’).
365365

366+
When determining the composite order in order to sort transition events
367+
where either or both of the events is a {{transitioncancel}} event,
368+
use the [=owning element=] and [=transition generation=]
369+
that were set immediately prior to cancelling the transition.
370+
366371
Transitions generated using the markup defined in this specification are
367372
<em>not</em> added to the <a>global animation list</a> when they are created.
368373
Instead, these animations are appended to the <a>global animation list</a> at
@@ -372,7 +377,7 @@ Transitions that have been disassociated from their <a>owning element</a>
372377
but are still [=play state/idle=] do not have a defined
373378
composite order.
374379

375-
Note, this behavior relies on the fact that disassociating a transition
380+
Note: This behavior relies on the fact that disassociating a transition
376381
from its <a>owning element</a> always causes it to enter (or remain) in the
377382
[=play state/idle|idle play state=].
378383

0 commit comments

Comments
 (0)