Skip to content

Commit 12822d1

Browse files
committed
[css-transitions-2] Drop CSSTransition constructor
1 parent fbbb3b0 commit 12822d1

1 file changed

Lines changed: 5 additions & 55 deletions

File tree

css-transitions-2/Overview.bs

Lines changed: 5 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -97,8 +97,8 @@ The <dfn>owning element</dfn> of a transition refers to the element or
9797
pseudo-element to which the 'transition-property' property was applied that
9898
generated the animation.
9999

100-
If a transition was generated directly by script (e.g. using the
101-
{{CSSTransition}} constructor) then it has no <a>owning element</a>.
100+
If a transition was generated directly by script then it has no <a>owning
101+
element</a>.
102102

103103
If a transition generated using the markup defined in this specification is
104104
later disassociated from that markup because it is cancelled or replaced by
@@ -112,9 +112,9 @@ cancel an animation).
112112

113113
## Animation composite order ## {#animation-composite-order}
114114

115-
<a spec='web-animations'>Animations</a> generated from the markup and
116-
interfaces (e.g. the {{CSSTransition}} constructor) defined in this
117-
specification have an <a>animation class</a> of &lsquo;CSS Transition&rsquo;.
115+
<a spec='web-animations'>Animations</a> generated from the markup defined in
116+
this specification have an <a>animation class</a> of &lsquo;CSS
117+
Transition&rsquo;.
118118

119119
CSS Transitions have an <em>earlier</em> composite order that CSS Animations
120120
and animations without a specific <a>animation class</a>.
@@ -165,9 +165,6 @@ Note, this behavior relies on the fact that disassociating a transition
165165
from its <a>owning element</a> always causes it to enter (or remain) in the
166166
<a>idle play state</a>.
167167

168-
Transitions created using the {{CSSTransition}} constructor are appended
169-
to the <a>global animation list</a> at the moment they are constructed.
170-
171168
# Transition Events # {#transition-events}
172169

173170
## Event dispatch ## {#event-dispatch}
@@ -362,53 +359,6 @@ interface CSSTransition : Animation {
362359
: <dfn attribute for=CSSTransition>transitionProperty</dfn>
363360
:: The <a>expanded transition property name</a> of this transition.
364361

365-
<div class="issue">
366-
367-
This interface needs a constructor. Perhaps something like the following,
368-
369-
<pre class="idl">
370-
partial interface CSSTransition {
371-
constructor(Animatable? target,
372-
CSSOMString transitionProperty,
373-
any transitionValue,
374-
optional (unrestricted double or KeyframeEffectOptions) options);
375-
constructor(Animatable? target,
376-
CSSOMString transitionProperty,
377-
any transitionValue,
378-
(unrestricted double or KeyframeEffectOptions) options,
379-
AnimationTimeline? timeline);
380-
};
381-
</pre>
382-
383-
Using <code>any</code> as the type for <code>transitionValue</code> would allow
384-
the following usage:
385-
386-
<pre class="example lang-javascript">
387-
var transition = new CSSTransition(elem, 'opacity', 1, 2000);
388-
transition.play();
389-
</pre>
390-
391-
The above example, however, is <em>not</em> equivalent to triggering a
392-
transition. It has the following differences:
393-
394-
* It does not update the specified style.
395-
* It would not cancel any existing transition on the given property unless
396-
we add special wording to that effect.
397-
* It would exhibit different composite order to a regular transition
398-
(this should be easily fixed, however).
399-
* It has been suggested that <a
400-
href="https://github.com/w3c/web-animations/issues/62#issuecomment-117357703">script-generated
401-
animations should not apply to the transition level of the cascade</a>.
402-
403-
It is unclear how much we should extend the {{CSSTransition}} constructor to
404-
overcome the above limitations so that it can be used to generate transitions
405-
programmatically, or whether we should introduce a separate helper method such
406-
as has been <a
407-
href="https://lists.w3.org/Archives/Public/www-style/2011Mar/0729.html">suggested
408-
elsewhere</a>.
409-
410-
</div>
411-
412362
## Requirements on pending style changes ## {#requirements-on-pending-style-changes}
413363

414364
Various operations may affect the <a lt="computed value">computed values</a> of

0 commit comments

Comments
 (0)