8000 csswg-drafts/css3-transitions/Overview.src.html at 1aa98500a61699f600d3525ed9c2970e25fca432 · xfq/csswg-drafts · GitHub
Skip to content

Overview.src.html

Latest commit

 

History

History
1451 lines (1385 loc) · 52.3 KB

Overview.src.html

File metadata and controls

1451 lines (1385 loc) · 52.3 KB
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01//EN'
'http://www.w3.org/TR/html4/strict.dtd'>
<html lang="en">
<head>
<title>CSS Transitions</title>
<link rel="stylesheet" type="text/css" href="../default.css">
<style type="text/css">
table.animatable-properties {
border-collapse: collapse;
}
table.animatable-properties td {
padding: 0.2em 1em;
border: 1px solid black;
}
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css">
</head>
<body>
<div class="head">
<!--logo-->
<h1>CSS Transitions</h1>
<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
<dt>This version:
<dd>
<a href="[VERSION]">
http://dev.w3.org/csswg/css3-transitions/</a>
<!--http://www.w3.org/TR/[YEAR]/WD-[SHORTNAME]-[CDATE]-->
<dt>Latest version:
<dd><a href="http://www.w3.org/TR/css3-transitions">
[LATEST]</a>
<dt>Editor's draft:
<dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a>
<dt>Previous version:
<dd><a href="http://www.w3.org/TR/2009/WD-css3-transitions-20091201/">
http://www.w3.org/TR/2009/WD-css3-transitions-20091201/</a>
<dt id="editors-list">Editors:
<dd><a href="mailto:dino@apple.com">Dean Jackson</a> (<a
href="http://www.apple.com/">Apple Inc</a>)
<dd><a href="mailto:hyatt@apple.com">David Hyatt</a> (<a
href="http://www.apple.com/">Apple Inc</a>)
<dd><a href="mailto:cmarrin@apple.com">Chris Marrin</a> (<a
href="http://www.apple.com/">Apple Inc</a>)
<dd class=vcard><a class=fn href="http://dbaron.org/">L. David Baron</a> (<a
class=org href="http://www.mozilla.com/">Mozilla</a>)
<dt>Issues list:
<dd><a href="https://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&amp;product=CSS&amp;component=Transitions&amp;resolution=---&amp;cmdtype=doit">in Bugzilla</a>
<dt>Discussion:</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> with subject line &ldquo;<kbd>[[SHORTNAME]] <var>&hellip; message topic &hellip;</var></kbd>&rdquo;
<dt>Test suite:
<dd>none yet
</dl>
<!--copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id="abstract">Abstract</h2>
<p>CSS Transitions allows property changes in CSS values to occur smoothly
over a specified duration.
<h2 class="no-num no-toc" id="status">Status of this document</h2>
<!--status-->
<p>
The <a href="ChangeLog">list of changes made to this specification</a> is
available.
</p>
<h2 class="no-num no-toc" id="contents">Table of contents</h2>
<!--toc-->
<h2 id="introduction">Introduction</h2>
<p><em>This section is not normative.</em>
<p>
This document introduces new CSS features to enable <em>implicit transitions</em>, which describe how CSS properties can be made to change smoothly from one value to another over a given duration.
</p>
<h2 id="transitions">Transitions</h2>
<p>
Normally when the value of a CSS property changes, the rendered result is instantly updated, with the affected elements immediately changing from the old property value to the new property value. This section describes a way to specify transitions using new CSS properties. These properties are used to animate smoothly from the old state to the new state over time.
</p>
<p>
For example, suppose that transitions of one second have been defined on the <code class="property">'left'</code> and
<code class="property">'background-color'</code> properties. The following diagram illustrates the effect of updating those properties on an element, in this case moving it to the right and changing the background from red to blue. This assumes other transition parameters still have their default values.
</p>
<div class="figure">
<img src="transition1.png" alt="">
</div>
<p class="caption">
Transitions of <code class="property">'left'</code> and <code class="property">'background-color'</code>
< D54 div id="LC104" class="react-file-line html-div" data-testid="code-cell" data-line-number="104" style="position:relative"> </p>
<p>
Transitions are a presentational effect. The computed value of a property transitions over time from the old value to the new value. Therefore if a script queries the computed style of a property as it is transitioning, it will see an intermediate value that represents the current animated value of the property.
</p>
<p>
Only animatable CSS properties can be transitioned. See the table at the end of this document for a list
of properties that are animatable.
</p>
<p>
The transition for a property is defined using a number of new properties. For example:
</p>
<div class="example">
<p style="display:none">
Example(s):
</p>
<pre>
div {
transition-property: opacity;
transition-duration: 2s;
}
</pre>The above example defines a transition on the <code class="property">'opacity'</code> property that, when a new value is assigned to it, will cause a smooth change between the old value and the new value over a period of two seconds.
</div>
<p>
Each of the transition properties accepts a comma-separated list, allowing multiple transitions to be defined, each acting on a different property. In this case, the individual transitions take their parameters from the same index in all the lists. For example:
</p>
<div class="example">
<p style="display:none">
Example(s):
</p>
<pre>
div {
transition-property: opacity, left;
transition-duration: 2s, 4s;
}
</pre>This will cause the <code class="property">'opacity'</code> property to transition over a period of two seconds and the left property to transition over a period of four seconds.
</div>
<p id="list-matching">
In the case where the lists of values in transition properties
do not have the same length, the length of the
'transition-property' list determines the number of items in
each list examined when starting transitions. The lists are
matched up from the first value: excess values at the end are
not used. If one of the other properties doesn't have enough
comma-separated values to match the number of values of
'transition-property', the UA must calculate its used value by
repeating the list of values until there are enough. This
truncation or repetition does not affect the computed value.
<span class="note">
Note: This is analogous to the behavior of the 'background-*'
properties, with 'background-image' analogous to
'transition-property'.
</span>
</p>
<div class="example">
<p style="display:none">
Example(s):
</p>
<pre>
div {
transition-property: opacity, left, top, width;
transition-duration: 2s, 1s;
}
</pre>The above example defines a transition on the <code class="property">'opacity'</code> property of 2 seconds duration, a
transition on the <code class="property">'left'</code> property of 1
second duration, a transition on the <code class="property">'top'</code> property of 2 seconds duration and a
transition on the <code class="property">'width'</code> property of 1
second duration.
</div>
<!-- ======================================================================================================= -->
<h3>
The <code class="property">'transition-property'</code> Property
</h3>
<p>
The <code class="property">'transition-property'</code> property specifies the name of the CSS property to which the transition is applied.
</p>
<div class="issue">
We may ultimately want to support a keypath syntax for this property. A keypath syntax would enable different transitions to be specified for components of a property. For example the blur of a shadow could have a different transition than the color of a shadow.
</div>
<table class="propdef">
<tbody>
<tr>
<td>
<em>Name:</em>
</td>
<td>
<dfn id="transition-property">transition-property</dfn>
</td>
</tr>
<tr>
<td>
<em>Value:</em>
</td>
<td>
none | [ all | &lt;IDENT&gt; ] [ ',' all | &lt;IDENT&gt; ]*
</td>
</tr>
<tr>
<td>
<em>Initial:</em>
</td>
<td>
all
</td>
</tr>
<tr>
<td>
<em>Applies&nbsp;to:</em>
</td>
<td>
all elements, :before and :after pseudo elements
</td>
</tr>
<tr>
<td>
<em>Inherited:</em>
</td>
<td>
no
</td>
</tr>
<tr>
<td>
<em>Percentages:</em>
</td>
<td>
N/A
</td>
</tr>
<tr>
<td>
<em>Media:</em>
</td>
<td>
visual
</td>
</tr>
<tr>
<td>
<em>Computed value:</em>
</td>
<td>
Same as specified value.
</td>
</tr>
</tbody>
</table>
<p>
A value of 'none' means that no property will transition.
Otherwise, a list of properties to be transitioned, or the
keyword 'all' which indicates that all properties are to be
transitioned, is given.
</p>
<p>
If one of the identifiers listed is not a recognized property
name or is not an animatable property, the implementation must
still start transitions on the animatable properties in the
list using the duration, delay, and timing function at their
respective indices in the lists for 'transition-duration',
'transition-delay', and 'transition-timing-function'. In other
words, unrecognized or non-animatable properties must be kept in
the list to preserve the matching of indices.
</p>
<p class="issue">
Are 'none', 'inherit', and 'initial' allowed as items in
a list of identifiers (of length greater than one)?
</p>
<p>
For the keyword 'all', or if one of the identifiers listed is a
shorthand property, implementations must start transitions for
any of its longhand sub-properties that are animatable (or, for
'all', all animatable properties), using the duration, delay,
and timing function at the index corresponding to the shorthand.
</p>
<p>
If a property is specified multiple times in the value of
'transition-property' (either on its own, via a shorthand that
contains it, or via the 'all' value), then the transition that
starts uses the duration, delay, and timing function at the
index corresponding to the <em>last</em> item in the value of
'transition-property' that calls for animating that property.
</p>
<p class="note">
Note: The <code class="property">all</code> value and shorthand
properties work in similar ways, so the <code
class="property">all</code> value is just like a shorthand that
covers all properties.
</p>
<!-- ======================================================================================================= -->
<h3>
The <code class="property">'transition-duration'</code> Property
</h3>
<p>
The <code class="property">'transition-duration'</code> property defines the length of time that a transition takes.
</p>
<table class="propdef">
<tbody>
<tr>
<td>
<em>Name:</em>
</td>
<td>
<dfn id="transition-duration">transition-duration</dfn>
</td>
</tr>
<tr>
<td>
<em>Value:</em>
</td>
<td>
&lt;time&gt; [, &lt;time&gt;]*
</td>
</tr>
<tr>
<td>
<em>Initial:</em>
</td>
<td>
0s
</td>
</tr>
<tr>
<td>
<em>Applies&nbsp;to:</em>
</td>
<td>
all elements, :before and :after pseudo elements
</td>
</tr>
<tr>
<td>
<em>Inherited:</em>
</td>
<td>
no
</td>
</tr>
<tr>
<td>
<em>Percentages:</em>
</td>
<td>
N/A
</td>
</tr>
<tr>
<td>
<em>Media:</em>
</td>
<td>
interactive
</td>
< D4C div>
</tr>
<tr>
<td>
<em>Computed value:</em>
</td>
<td>
Same as specified value.
</td>
</tr>
</tbody>
</table>
<p>
This property specifies how long the transition from the old value to the new value should take. By default the value is '0s', meaning that the transition is immediate (i.e. there will be no animation). A negative value for <code class="property">transition-duration</ 8097 code> is treated as '0s'.
</p>
<!-- =======================================================================================================
-->
<h3 id="transition-timing-function_tag">
The <code class="property">'transition-timing-function'</code> Property
</h3>
<p>
The <code class="property">'transition-timing-function'</code> property
describes how the intermediate values used during a transition will be
calculated. It allows for a transition to change speed over its
duration. These effects are commonly called <em>easing</em> functions.
In either case, a mathematical function that provides a smooth curve is
used.
</p>
<p>
Timing functions are either defined as a stepping function or
a <a
href="http://en.wikipedia.org/wiki/B%C3%A9zier_curve#Cubic_B.C3.A9zier_curves">cubic
B&eacute;zier curve</a>.
The timing function takes as its input the current elapsed percentage of
the transition duration and outputs a percentage that determines how
close the transition is to its goal state.
</p>
<p>
A <a href="http://en.wikipedia.org/wiki/Step_function">stepping</a>
function is defined by a number that divides the domain of operation
into equally sized intervals. Each subsequent interval is a equal step
closer to the goal state. The function also specifies whether the
change in output percentage happens at the start or end of the
interval (in other words, if 0% on the input percentage is the point
of initial change).
</p>
<div class="figure">
<img src="step.png" alt="The step timing function splits
the function domain into a number of disjoint straight line
segments. steps(1, start) is a function whose
output value is 1 for all input values. steps(1, end) is a function whose
output value is 0 for all input values less than 1, and output
is 1 for the input value of 1. steps(3, start) is a function that
divides the input domain into three segments, each 1/3 in length,
and 1/3 above the previous segment, with the first segment starting
at 1/3. steps(3, end) is a function that
divides the input domain into three segments, each 1/3 in length,
and 1/3 above the previous segment, with the first segment starting
at 0.">
</div>
<p class="caption">
Step timing functions
</p>
<p>
A <a
href="http://en.wikipedia.org/wiki/B%C3%A9zier_curve#Cubic_B.C3.A9zier_curves">cubic
B&eacute;zier curve</a> is defined by four control points, P<sub>0</sub>
through P<sub>3</sub> (see Figure 1). P<sub>0</sub> and P<sub>3</sub>
are always set to (0,0) and (1,1). The <code class="property">'transition-timing-function'</code> property is used
to specify the values for points P<sub>1</sub> and P<sub>2</sub>. These
can be set to preset values using the keywords listed below, or can be
set to specific values using the <code class="css">'cubic-bezier'</code> function.
In the <code class="css">'cubic-bezier'</code> function, P<sub>1</sub> and
P<sub>2</sub> are each specified by both an X and Y value.
</p>
<div class="figure">
<img src="TimingFunction.png" alt="The B&eacute;zier timing function is a
smooth curve from point P0 = (0,0) to point P3 = (1,1). The
length and orientation of the line segment P0-P1 determines
the tangent and the curvature of the curve at P0 and the
line segment P2-P3 does the same at P3.">
</div>
<p class="caption">
B&eacute;zier Timing Function Control Points
</p>
<table class="propdef">
<tbody>
<tr>
<td>
<em>Name:</em>
</td>
<td>
<dfn id="transition-timing-function">transition-timing-function</dfn>
</td>
</tr>
<tr>
<td>
<em>Value:</em>
</td>
<td>
ease | linear | ease-in | ease-out | ease-in-out | step-start | step-end | steps(&lt;integer&gt;[, start | end ]) | cubic-bezier(&lt;number&gt;, &lt;number&gt;, &lt;number&gt;, &lt;number&gt;) [, ease | linear | ease-in | ease-out | ease-in-out | step-start | step-end | steps(&lt;number&gt;[, start | end ]) | cubic-bezier(&lt;number&gt;, &lt;number&gt;, &lt;number&gt;, &lt;number&gt;)]*
</td>
</tr>
<tr>
<td>
<em>Initial:</em>
</td>
<td>
ease
</td>
</tr>
<tr>
<td>
<em>Applies&nbsp;to:</em>
</td>
<td>
all elements, :before and :after pseudo elements
</td>
</tr>
<tr>
<td>
<em>Inherited:</em>
</td>
<td>
no
</td>
</tr>
<tr>
<td>
<em>Percentages:</em>
</td>
<td>
7DDD
N/A
</td>
</tr>
<tr>
<td>
<em>Media:</em>
</td>
<td>
interactive
</td>
</tr>
<tr>
<td>
<em>Computed value:</em>
</td>
<td>
Same as specified value.
</td>
</tr>
</tbody>
</table>
<p>
The timing functions have the following definitions.
</p>
<dl>
<dt>
ease
</dt>
<dd>
The ease function is equivalent to cubic-bezier(0.25, 0.1, 0.25, 1.0).
</dd>
<dt>
linear
</dt>
<dd>
The linear function is equivalent to cubic-bezier(0.0, 0.0, 1.0, 1.0).
</dd>
<dt>
ease-in
</dt>
<dd>
The ease-in function is equivalent to cubic-bezier(0.42, 0, 1.0, 1.0).
</dd>
<dt>
ease-out
</dt>
<dd>
The ease-out function is equivalent to cubic-bezier(0, 0, 0.58, 1.0).
</dd>
<dt>
ease-in-out
</dt>
<dd>
The ease-in-out function is equivalent to cubic-bezier(0.42, 0, 0.58, 1.0)
</dd>
<dt>
step-start
</dt>
<dd>
The step-start function is equivalent to steps(1, start).
</dd>
<dt>
step-end
</dt>
<dd>
The step-end function is equivalent to steps(1, end).
</dd>
<dt>
steps
</dt>
<dd>
Specifies a stepping function, described above, taking two
parameters. The first parameter specifies the number of intervals
in the function. It must be a positive integer (greater than 0).
The second parameter, which is optional, is
either the value 'start' or 'end', and specifies the point
at which the change of values occur within the interval.
If the second parameter is omitted, it is given the value 'end'.
</dd>
<dt>
cubic-bezier
</dt>
<dd>
Specifies a <a
href="http://en.wikipedia.org/wiki/B%C3%A9zier_curve">cubic-bezier
curve</a>. The four values specify points P<sub>1</sub> and
P<sub>2</sub> of the curve as (x1, y1, x2, y2). Both x values must be
in the range [0, 1] or the definition is invalid. The y values can
exceed this range.
</dd>
</dl><!-- ======================================================================================================= -->
<h3>
The <code class="property">'transition-delay'</code> Property
</h3>
<p>
The <code class="property">'transition-delay'</code> property defines when the transition will start. It allows a transition to begin execution some some period of time from when it is applied. A <code class="property">'transition-delay'</code> value of '0s' means the transition will execute as soon as the property is changed. Otherwise, the value specifies an offset from the moment the property is changed, and the transition will delay execution by that offset.
</p>
<p>
If the value for <code class="property">'transition-delay'</code> is a negative time offset then the transition will execute the moment the property is changed, but will appear to have begun execution at the specified offset. That is, the transition will appear to begin part-way through its play cycle. In the case where a transition has implied starting values and a negative <code class="property">'transition-delay'</code>, the starting values are taken from the moment the property is changed.
</p>
<table class="propdef">
<tbody>
<tr>
<td>
<em>Name:</em>
</td>
<td>
<dfn id="transition-delay">transition-delay</dfn>
</td>
</tr>
<tr>
<td>
<em>Value:</em>
</td>
<td>
&lt;time&gt; [, &lt;time&gt;]*
</td>
</tr>
<tr>
<td>
<em>Initial:</em>
</td>
<td>
0s
</td>
</tr>
<tr>
<td>
<em>Applies&nbsp;to:</em>
</td>
<td>
all elements, :before and :after pseudo elements
</td>
</tr>
<tr>
<td>
<em>Inherited:</em>
</td>
<td>
no
</td>
</tr>
<tr>
<td>
<em>Percentages:</em>
</td>
<td>
N/A
</td>
</tr>
<tr>
<td>
<em>Media:</em>
</td>
<td>
interactive
</td>
</tr>
<tr>
<td>
<em>Computed value:</em>
</td>
<td>
Same as specified value.
</td>
</tr>
</tbody>
</table><!-- ======================================================================================================= -->
<h3>
The <code class="property">'transition'</code> Shorthand Property
</h3>
<p>
The <code class="property">'transition'</code> shorthand property combines the four properties described above into a single property.
</p>
<p>
Note that order is important in this property. The first value that can be
parsed as a time is assigned to the transition-duration. The second value that
can be parsed as a time is assigned to transition-delay.
</p>
<p class="issue">
An alternative proposal is to accept the font shorthand approach of
using a "/" character between the values of the same type. e.g. 2s/4s would
mean a duration of 2 seconds and a delay of 4 seconds.
</p>
<table class="propdef">
<tbody>
<tr>
<td>
<em>Name:</em>
</td>
<td>
<dfn id="transition">transition</dfn>
</td>
</tr>
<tr>
<td>
<em>Value:</em>
</td>
<td>
[&lt;'transition-property'&gt; || &lt;'transition-duration'&gt; || &lt;'transition-timing-function'&gt; || &lt;'transition-delay'&gt; [, [&lt;'transition-property'&gt; || &lt;'transition-duration'&gt; || &lt;'transition-timing-function'&gt; || &lt;'transition-delay'&gt;]]*
</td>
</tr>
<tr>
<td>
<em>Initial:</em>
</td>
<td>
see individual properties
</td>
</tr>
<tr>
<td>
<em>Applies&nbsp;to:</em>
</td>
<td>
all elements, :before and :after pseudo elements
</td>
</tr>
<tr>
<td>
<em>Inherited:</em>
</td>
<td>
no
</td>
</tr>
<tr>
<td>
<em>Percentages:</em>
</td>
<td>
N/A
</td>
</tr>
<tr>
<td>
<em>Media:</em>
</td>
<td>
interactive
</td>
</tr>
<tr>
<td>
<em>Computed value:</em>
</td>
<td>
Same as specified value.
</td>
</tr>
</tbody>
</table>
<h2 id="starting">
Starting of transitions
</h2>
<p>
When the computed value of an animatable property changes,
implementations must decide what transitions to start based on
the values of the 'transition-property', 'transition-duration',
'transition-timing-function', and 'transition-delay' properties
at the time the animatable property would first have its new
computed value.
</p>
<div class="example" id="manual-reversing-example">
<p style="display:none">
Example(s):
</p>
<p>This provides a way for authors to specify different values
of the 'transition-*' properties for the &ldquo;forward&rdquo;
and &ldquo;reverse&rdquo; transitions (but see <a
href="#reversing">below</a> for special reversing behavior when
an <em>incomplete</em> transition is interrupted). Authors can
specify the value of 'transition-duration',
'transition-timing-function', or 'transition-delay' in the same
rule where they specify the value that triggers the transition,
or can change these properties at the same time as they change
the property that triggers the transition. Since it's the new
values of these 'transition-*' properties that affect the
transition, these values will be used for the transitions
<em>to</em> the associated transitioning values. For example:
</p>
<pre>li {
transition: background-color linear 1s;
background: blue;
}
li:hover {
background-color: green;
transition-duration: 2s; /* applies to the transition *to* the :hover state */
}</pre>
<p>
When a list item with these style rules enters the :hover
state, the computed 'transition-duration' at the time that
'background-color' would have its new value ('green') is '2s',
so the transition from 'blue' to 'green' takes 2 seconds.
However, when the list item leaves the :hover state, the
transition from 'green' to 'blue' takes 1 second.
</p>
</div>
<p>
When the computed value of a property changes, implementations
must start transitions based on the relevant item (see <a
href="#transition-property">the definition of
'transition-property'</a>) in the computed value of
'transition-property'. Corresponding to this item there are
values of 'transition-duration' and 'transition-delay' (see <a
href="#list-matching">the rules on matching lists</a>). Define
the <dfn>combined duration</dfn> of the transition as the sum of
max('transition-duration', '0s') and 'transition-delay'. When
the combined duration is greater than '0s', then a transition
starts based on the values of 'transition-duration',
'transition-delay', and 'transition-timing-function'; in other
cases transitions do not occur.
</p>
<p>
Since this specification does not define
when computed values change, and thus what changes to
computed values are considered simultaneous,
authors should be aware that changing any of the transition
properties a small amount of time after making a change that
might transition can result in behavior that varies between
implementations, since the changes might be considered
simultaneous in some implementations but not others.
</p>
<p class="note">Say something about simultaneity</p>
<p>
Once the transition of a property has started, it must continue
running based on the original timing function, duration, and
delay, even if the 'transition-timing-function',
'transition-duration', or 'transition-delay' property changes
before the transition is complete. However, if the
'transition-property' property changes such that the transition
would not have started, the transition must stop (and the
property must immediately change to its final value).
</p>
<p>
Implementations must not start a transition when the computed
value of a property changes as a result of declarative animation
(as opposed to scripted animation).
</p>
<p>
Implementations also must not start a transition when the
computed value changes because it is inherited (directly or
indirectly) from another element that is transitioning the same
property.
</p>
<h2 id="reversing">
Automatically reversing interrupted transitions
</h2>
<p>
A common type of transition effect is when a running transition is
interrupted and the property is reset to its original value. An
example is a hover effect on an element, where the pointer enters and
exits the element before the effect has completed. If the outgoing and
incoming transitions are executed using their specified durations and
timing functions, the resulting effect can be distractingly
asymmetric. Instead, the expected behavior is that the new transition
should be the reverse of what has already executed.
</p>
<p>
If a running transition with duration T, executing so far for duration TE,
from state A, to state B, is interrupted by
a property change that would start a new transition back to state A, and
all the transition attributes are the same (duration, delay and timing function),
then the new transition must reverse the effect. The new transition must:
</p>
<ol>
<li>
Use the B and A states as its "from" and "to" states respectively. It
does not use the current value as its from state, due to the rules below.
</li>
<li>
Execute with the same duration T, but starting as if the transition had
already begu B283 n, without any transition delay, at the moment which would
cause the new transition to finish in TE from the moment of interruption. In other
words, the new transition will execute as if it started T-TE in the past.
</li>
<li>
Use a timing function that is the portion of the curve traversed up
to the moment of interruption, followed in the opposite direction (towards
the starting point). This will make the transition appear as if it
is playing backwards.
</li>
<li>
Ignore any transition delay.
</li>
</ol>
<p>
For example, suppose there is a transition with a duration of two
seconds. If this transition is interrupted after 0.5 seconds and the
property value assigned to the original value, then the new transition
effect will be the reverse of the original, as if it had begun
1.5 seconds in the past.
</p>
<p>
Note that by using the defined from and to states for the reversing
transition, it is also possible that it may reverse again, if
interrupted; for example, if the transition reversing to state A was
again interrupted by a property change to state B.
</p>
<p class="issue">Issue:
This introduces the concept of reversing a timing function,
which the spec has otherwise resisted doing, and also introduces
a discontinuity between transitions that have
almost completed (which get automatically reversed and thus have
their timing function reversed) and transitions that have fully
completed (where the reversal doesn't lead to the timing
function being reversed). An alternative proposal that avoids
this is to follow the normal timing function algorithm, except
multiply the duration (and also shorten any negative delay) by
the (output) value of the transition timing function of the
incomplete transition at the time it was interrupted, and, to
account for multiple reverses in sequence, to divide by the
shortening applied to the transition being interrupted. For
more details see this thread:
<a href="http://lists.w3.org/Archives/Public/www-style/2009Nov/thread.html#msg302">November 2009 part</a>,
<a href="http://lists.w3.org/Archives/Public/www-style/2009Dec/thread.html#msg319">December 2009 part</a>,
<a href="http://lists.w3.org/Archives/Public/www-style/2010Jan/thread.html#msg136">January 2010 part</a>.
</p>
<h2>
Transition Events
</h2>
<p>
The completion of a CSS Transition generates a corresponding <a href="http://www.w3.org/TR/DOM-Level-2-Events/events.html">DOM Event</a>.
An event is fired for each property that undergoes a transition.
This allows a content developer to perform actions that synchronize
with the completion of a transition.
</p>
<p>
Each event provides the name of the property the transition is
associated with as well as the duration of the transition.
</p>
<dl>
<dt>
<b>Interface <i><a id="Events-TransitionEvent" name='Events-TransitionEvent'>TransitionEvent</a></i></b>
</dt>
<dd>
<p>
The <code>TransitionEvent</code> interface provides specific contextual information associated with transitions.
</p>
<dl>
<dt>
<b>IDL Definition</b>
</dt>
<dd>
<div class='idl-code'>
<pre>
interface TransitionEvent : Event {
readonly attribute DOMString propertyName;
readonly attribute float elapsedTime;
void initTransitionEvent(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
in DOMString propertyNameArg,
in float elapsedTimeArg);
};
</pre>
</div>
</dd>
<dt>
<b>Attributes</b>
</dt>
<dd>
<dl>
<dt>
<code class='attribute-name'><a id="Events-TransitionEvent-propertyName" name='Events-TransitionEvent-propertyName'>propertyName</a></code> of type <code>DOMString</code>, readonly
</dt>
<dd>
The name of the CSS property associated with the transition.
</dd>
</dl>
<dl>
<dt>
<code class='attribute-name'><a id="Events-TransitionEvent-elapsedTime" name='Events-TransitionEvent-elapsedTime'>elapsedTime</a></code> of type <code>float</code>, readonly
</dt>
<dd>
The amount of time the transition has been running, in seconds, when this event fired. Note that this value is not affected by the value of <code class="property">transition-delay</code>.
</dd>
</dl>
</dd>
<dt>
<b>Methods</b>
</dt>
<dd>
<dl>
<dt>
<code class='method-name'><a id="Events-TransitionEvent-initTransitionEvent" name='Events-TransitionEvent-initTransitionEvent'>initTransitionEvent</a></code>
</dt>
<dd>
<div class='method'>
The <code>initTransitionEvent</code> method is used to
initialize the value of a <code>TransitionEvent</code>
View remainder of file in raw view