Skip to content

Commit 0b25667

Browse files
committed
[css-transitions-2] Specify interaction between running transitions and Web Animations API
Fixes w3c#3233. The mention of `display:none` handling (the "not rendered" part) is intended to address issue w3c#2948 and should ultimately be integrated into level 1.
1 parent d0fa0af commit 0b25667

File tree

1 file changed

+25
-9
lines changed

1 file changed

+25
-9
lines changed

css-transitions-2/Overview.bs

Lines changed: 25 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,7 @@ urlPrefix: https://drafts.csswg.org/web-animations/; type: dfn; spec: web-animat
4040
text: animation effect
4141
text: animation class
4242
text: animation playback rate
43+
text: cancel an animation
4344
text: current iteration
4445
text: current time
4546
text: fill mode
@@ -53,9 +54,12 @@ urlPrefix: https://drafts.csswg.org/web-animations/; type: dfn; spec: web-animat
5354
text: target effect
5455
text: target effect end
5556
text: unresolved
57+
urlPrefix: https://html.spec.whatwg.org/multipage/browsers.html; type: dfn; spec: html
58+
text: being rendered
5659
</pre>
5760
<pre class=link-defaults>
5861
spec:css-transitions-1; type:value; text:all
62+
spec:css-transitions-1; type:dfn; text:cancel
5963
</pre>
6064

6165
<h2 id="delta">Delta specification</h2>
@@ -81,6 +85,25 @@ the reversing shortening factor.
8185

8286
# Starting of transitions # {#starting}
8387

88+
The set of [=running transitions=] includes
89+
only those transitions that have an [=owning element=].
90+
91+
Whenever an implementation is required to [=cancel=] a transition,
92+
it must disassociate the transition from its [=owning element=]
93+
and run the procedure to [=cancel an animation=] on the transition.
94+
95+
Although not explicitly defined by level 1 of this specification,
96+
in addition to [=cancel|cancelling=] transitions on elements that
97+
are no longer [=connected=],
98+
implementations must also [=cancel=] any running transitions
99+
on elements that are no longer [=being rendered=] and
100+
remove transitions on them from the set of [=completed transitions=].
101+
102+
Note that calling the {{Animation/cancel()}} method
103+
on the {{CSSTransition}} object representing a [=running transition=]
104+
does <em>not</em> cause the transition to be disassociated
105+
from its [=owning element=].
106+
84107
## The current transition generation ## {#current-transition-generation-section}
85108

86109
Associated with each top-level browsing context is a <dfn>current transition
@@ -104,15 +127,8 @@ The <dfn>owning element</dfn> of a transition refers to the element or
104127
pseudo-element to which the 'transition-property' property was applied that
105128
generated the animation.
106129

107-
If a transition generated using the markup defined in this specification is
108-
later disassociated from that markup because it is cancelled or replaced by
109-
a newer transition, the animation is disassociated from its <a>owning
110-
element</a> (that is, it has no <a>owning element</a> from that point
111-
forwards).
112-
113-
Issue: Define the above more precisely once we rewrite firing of transitions
114-
in terms of Web Animations concepts (specifically when we spell out when we
115-
cancel an animation).
130+
A transition may be disassociated from its [=owning element=]
131+
such that it has no [=owning element=].
116132

117133
# Application of transitions # {#application}
118134

0 commit comments

Comments
 (0)