drafts: css3-transitions/Overview.src.html@6013bb8b5fe9 (annotated)

css3-transitions/Overview.src.html@6013bb8b5fe9 (annotated)

css3-transitions/Overview.src.html

Mon, 14 Jan 2013 16:29:21 -0800

author: Tab Atkins <jackalmage@gmail.com>
date: Mon, 14 Jan 2013 16:29:21 -0800
changeset 7183: 6013bb8b5fe9
parent 7182: a38c76f0336b
child 7297: e941140de034
permissions: -rw-r--r--

[css3-transitions] markup tweak - quote all the id values, so ST2 syntax highlighting works correctly.

 <!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>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <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;
     }
     div.prod { margin: 1em 2em; }
   </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/2012/WD-css3-transitions-20120403/">
       http://www.w3.org/TR/2012/WD-css3-transitions-20120403/</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.org/">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"><a id="transitions-">Transitions</a></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>
       </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 id="transition-property-property"><a id="the-transition-property-property-">
         The <code class="property">'transition-property'</code> Property
       </a></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 | <span>&lt;single-transition-property&gt;</span> [ ',' <span>&lt;single-transition-property&gt;</span> ]*
             </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>Animatable:</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>
           <tr>
             <td>
               <em>Canonical order:</em>
             </td>
             <td>
               <abbr title="follows order of property value definition">per grammar</abbr>
             </td>
           </tr>
         </tbody>
       </table>
       <div class="prod">
         <dfn id="single-transition-property">&lt;single-transition-property&gt;</dfn> = all | &lt;IDENT&gt;
       </div>
       <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 id="transition-duration-property"><a id="the-transition-duration-property-">
         The <code class="property">'transition-duration'</code> Property
       </a></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>
               <span>&lt;time&gt;</span> [, <span>&lt;time&gt;</span>]*
             </td>
           </tr>
           <tr>
             <td>
               <em>Initial:</em>
             </td>
             <td>
 s
             </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>Animatable:</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>
           <tr>
             <td>
               <em>Canonical order:</em>
             </td>
             <td>
               <abbr title="follows order of property value definition">per grammar</abbr>
             </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</code> renders the declaration invalid.
       </p>
       <!-- =======================================================================================================
         -->
       <h3 id="transition-timing-function-property"><a id="transition-timing-function_tag">
         The <code class="property">'transition-timing-function'</code> Property
       </a></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 the percentage of the way the transition is
         from its start value to its end value.
         How this output is used is defined by
         the <a href="#animatable-types">interpolation rules</a>
         for the value type.
       </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>
               <span>&lt;single-transition-timing-function&gt;</span> [ ',' <span>&lt;single-transition-timing-function&gt;</span> ]*
             </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>Animatable:</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>
           <tr>
             <td>
               <em>Canonical order:</em>
             </td>
             <td>
               <abbr title="follows order of property value definition">per grammar</abbr>
             </td>
           </tr>
         </tbody>
       </table>
       <div class="prod">
         <dfn id="single-transition-timing-function">&lt;single-transition-timing-function&gt;</dfn> = 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;)
       </div>
       <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).
         </dd>
         <dt>
           linear
         </dt>
         <dd>
           The linear function is equivalent to cubic-bezier(0, 0, 1, 1).
         </dd>
         <dt>
           ease-in
         </dt>
         <dd>
           The ease-in function is equivalent to cubic-bezier(0.42, 0, 1, 1).
         </dd>
         <dt>
           ease-out
         </dt>
         <dd>
           The ease-out function is equivalent to cubic-bezier(0, 0, 0.58, 1).
         </dd>
         <dt>
           ease-in-out
         </dt>
         <dd>
           The ease-in-out function is equivalent to cubic-bezier(0.42, 0, 0.58, 1)
         </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(&lt;integer&gt;[, [ start | end ] ]?)
         </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(&lt;number&gt;, &lt;number&gt;, &lt;number&gt;, &lt;number&gt;)
         </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 id="transition-delay-property"><a id="the-transition-delay-property-">
         The <code class="property">'transition-delay'</code> Property
       </a></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>
               <span>&lt;time&gt;</span> [, <span>&lt;time&gt;</span>]*
             </td>
           </tr>
           <tr>
             <td>
               <em>Initial:</em>
             </td>
             <td>
 s
             </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>Animatable:</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>
           <tr>
             <td>
               <em>Canonical order:</em>
             </td>
             <td>
               <abbr title="follows order of property value definition">per grammar</abbr>
             </td>
           </tr>
         </tbody>
       </table><!-- ======================================================================================================= -->
       <h3 id="transition-shorthand-property"><a id="the-transition-shorthand-property-">
         The <code class="property">'transition'</code> Shorthand Property
       </a></h3>
       <p>
         The <code class="property">'transition'</code> shorthand property combines the four properties described above into a single property.
       </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>
               <span>&lt;single-transition&gt;</span> [ ',' <span>&lt;single-transition&gt;</span> ]*
             </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>Animatable:</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>
           <tr>
             <td>
               <em>Canonical order:</em>
             </td>
             <td>
               <abbr title="follows order of property value definition">per grammar</abbr>
             </td>
           </tr>
         </tbody>
       </table>
       <div class="prod">
         <dfn id="single-transition">&lt;single-transition&gt;</dfn> = [ none | <span>&lt;single-transition-property&gt;</span> ] || <span>&lt;time&gt;</span> || <span>&lt;single-transition-timing-function&gt;</span> || <span>&lt;time&gt;</span>
       </div>
       <p>
         Note that order is important within the items in this property:
         the first value that can be parsed as a time is assigned to the
         transition-duration,
         and 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>
       <p>
         If there is more than one <span>&lt;single-transition&gt;</span> in the shorthand,
         and any of the transitions has
         ''none'' as the <span>&lt;single-transition-property&gt;</span>,
         then the declaration is invalid.
       </p>
       <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
         computed 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 begun, 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
 .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 id="transition-events"><a id="transition-events-">
         Transition Events
       </a></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;
     readonly attribute DOMString          pseudoElement;
     void               initTransitionEvent(in DOMString typeArg,
                                           in boolean canBubbleArg,
                                           in boolean cancelableArg,
                                           in DOMString propertyNameArg,
                                           in float elapsedTimeArg,
                                           in DOMString pseudoElementArg);
   };
   </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>
               <dl>
                 <dt>
                   <code class='attribute-name'><a id="Events-TransitionEvent-pseudoElement" name='Events-TransitionEvent-pseudoElement'>pseudoElement</a></code> of type <code>DOMString</code>, readonly
                 </dt>
                 <dd>
                   The name (beginning with two colons) of the CSS
                   pseudo-element on which the transition occured (in
                   which case the target of the event is that
                   pseudo-element's corresponding element), or the empty
                   string if the transition occurred on an element (which
                   means the target of the event is that element).
                 </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>
                     created through the <a
                     href='http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-DocumentEvent'><code>DocumentEvent</code></a>
                     interface. This method may only be called before the
                     <code>TransitionEvent</code> has been dispatched via the
                     <code>dispatchEvent</code> method, though it may be called
                     multiple times during that phase if necessary. If called
                     multiple times, the final invocation takes precedence.
                     <p class="issue">Should new events being created still
                     have init*Event methods?</p>
                     <div class='parameters'>
                       <b>Parameters</b>
                       <div class='paramtable'>
                         <dl>
                           <dt>
                             <code class='parameter-name'>typeArg</code> of type <code>DOMString</code>
                           </dt>
                           <dd>
                             Specifies the event type.<br>
                           </dd>
                           <dt>
                             <code class='parameter-name'>canBubbleArg</code> of type <code>boolean</code>
                           </dt>
                           <dd>
                             Specifies whether or not the event can bubble.<br>
                           </dd>
                           <dt>
                             <code class='parameter-name'>cancelableArg</code> of type <code>boolean</code>
                           </dt>
                           <dd>
                             Specifies whether or not the event's default action can be prevented. Since a TransitionEvent
                             is purely for notification, there is no default action.<br>
                           </dd>
                           <dt>
                             <code class='parameter-name'>propertyNameArg</code> of type <code>DOMString</code>
                           </dt>
                           <dd>
                             Specifies the name of the property associated with the <a href='http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-Event'><code>Event</code></a>.
                             (See the <a href="#Events-TransitionEvent-propertyName">propertyName</a> attribute.)
                           </dd>
                           <dt>
                             <code class='parameter-name'>elapsedTimeArg</code> of type <code>float</code>
                           </dt>
                           <dd>
                             Specifies the amount of time, in seconds, the transition has been running at the time of initialization.
                             (See the <a href="#Events-TransitionEvent-elapsedTime">elapsedTime</a> attribute.)
                           </dd>
                           <dt>
                             <code class='parameter-name'>pseudoElementArg</code> of type <code>DOMString</code>
                           </dt>
                           <dd>
                             Specifies the pseudo-element on which the
                             transition occurred.
                             (See the <a href="#Events-TransitionEvent-pseudoElement">pseudoElement</a> attribute.)
                             <span class="issue">Does adding this additional argument create any compatibility problems?</span>
                           </dd>
                         </dl>
                       </div>
                     </div><!-- parameters -->
                     <div>
                       <b>No Return Value</b>
                     </div>
                     <div>
                       <b>No Exceptions</b>
                     </div>
                   </div><!-- method -->
                 </dd>
               </dl>
             </dd>
           </dl>
         </dd>
       </dl>
       <p>
         There is one type of transition event available.
       </p>
       <dl>
         <dt>
           <b>transitionend</b>
         </dt>
         <dd>
           The 'transitionend' event occurs at the completion of the transition. In the
           case where a transition is removed before completion, such as if the
           transition-property is removed, then the event will not fire.
           <ul>
             <li>Bubbles: Yes
             </li>
             <li>Cancelable: Yes
             </li>
             <li>Context Info: propertyName, elapsedTime
             </li>
           </ul>
         </dd>
       </dl>
       <h2 id="animatable-types"><a id="animation-of-property-types-">
         Animation of property types
       </a></h2>
       <p>
         When interpolating between two values,
         <i>V</i><sub>start</sub> and <i>V</i><sub>end</sub>,
         interpolation is done using the output <i>p</i> of the timing function,
         which gives the portion of the value space
         that the interpolation has crossed.
         Thus the result of the interpolation is
         <i>V</i><sub>res</sub> =
           (1 - <i>p</i>) &sdot; <i>V</i><sub>start</sub> +
           <i>p</i> &sdot; <i>V</i><sub>end</sub>.
       </p>
       <p>
         However, if this value (<i>V</i><sub>res</sub>)
         is outside the allowed range of values for the property,
         then it is clamped to that range.
         This can occur if <i>p</i> is outside of the range 0 to 1,
         which can occur if a timing function is specified
         with a <i>y1</i> or <i>y2</i> that is outside the range 0 to 1.
       </p>
       <p>
         The following describes how each property type undergoes transition or
         animation.
       </p>
       <ul>
         <li>
           <strong>color</strong>: interpolated via red, green, blue and alpha
           components (treating each as a number, see below).
           <div class="issue">Issue: Are the colors interpolated in
           premultiplied space or non-premultiplied space?</div>
         </li>
         <li>
           <strong>length</strong>: interpolated as real numbers.
         </li>
         <li>
           <strong>percentage</strong>: interpolated as real numbers.
         </li>
         <li>
           <strong>integer</strong>: interpolated via discrete steps (whole
           numbers). The interpolation happens in real number space and is
           converted to an integer using <code>floor()</code>.
           <span class="issue">
             This floor behavior is inconsistent with SMIL Animation /
             SVG Animation.
           </span>
         </li>
         <li>
           <strong>font weight</strong>: interpolated via discrete steps
           (multiples of 100). The interpolation happens in real number
           space and is converted to an integer by rounding to the
           nearest multiple of 100.
           <span class="issue">
             This round-to-nearest behavior is inconsistent with the
             floor behavior used for integer types, but probably should
             be consistent (one way or the other).
           </span>
         </li>
         <li>
           <strong>number</strong>: interpolated as real (floating point)
           numbers.
         </li>
         <li>
           <strong>transform list</strong>: see
             CSS Transforms specification [[!CSS3-TRANSFORMS]].
         </li>
         <li>
           <strong>rectangle</strong>: interpolated via the x, y,
           width and height components (treating each as a number).
         </li>
         <li>
           <strong>visibility</strong>: if one of the values is
           'visible', interpolated as a discrete step where values of the
           timing function between 0 and 1 map to 'visible' and other
           values of the timing function (which occur only at the
           start/end of the transition or as a result of 'cubic-bezier()'
           functions with Y values outside of [0, 1]) map to the closer
           endpoint; if neither value is 'visible' then not interpolable.
         </li>
         <li>
           <strong>shadow</strong>: interpolated via the color, x, y
           and blur components (treating them as color and numbers where
           appropriate). In the case where there are lists of shadows,
           the shorter list is padded at the end with shadows whose
           color is transparent and all lengths (x, y, blur) are 0.
         </li>
         <li>
           <strong>gradient</strong>: interpolated via the
           positions and colors of each stop. They must have the same type
           (radial or linear) and same number of stops in order to be animated.
           <span class="note">Note: [[CSS3-IMAGES]] may extend this
           definition.</span>
         </li>
         <li>
           <strong>paint server</strong> (SVG): interpolation is only supported
           between: gradient to gradient and color to color. They then
           work as above.
         </li>
         <li>
           <strong>list of above types</strong>: If the lists have the
           same number of items, each item in the list is interpolated using the
           rules above. Otherwise the interpolation is determined by the property
           rules. If the property extends its list by repeating values, then this
           repeated form will be used in the interpolation (<code class="property">'background-position'</code>
           is an example of a property that would transition between lists of different lengths). If
           the property does not allow extending its list, then no interpolation
           will occur.
         </li>
         <li>
           <strong>a shorthand property</strong>: If any part of a
           shorthand can be animated, then interpolation is performed as
           if those animatable properties were individually specified.
         </li>
       </ul>
       <p class="issue">Need to add a length-percentage-calc type.</p>
       <p>Future specifications may define additional types that can
       be animated.</p>
       <h2 id="animatable-properties"><a id="animatable-properties-">
         Animatable properties
       </a></h2>
       <!--
       As resolved in
       http://lists.w3.org/Archives/Public/www-style/2011Sep/0497.html
       -->
       <p>For properties that exist at the time this specification was
       developed, this specification defines whether and how they are
       animated.  However, future CSS specifications may define
       additional properties, additional values for existing properties,
       or additional animation behavior of existing values.  In order to
       describe new animation behaviors and to have the definition of
       animation behavior in a more appropriate location, future CSS
       specifications should include an "Animatable:" line in the summary
       of the property's definition (in addition to the other lines
       described in [[CSS21]], <a
       href="http://www.w3.org/TR/CSS21/about.html#property-defs">section
 .4.2</a>).  This line should say "no" to indicate that a property
       cannot be animated or should reference an animation behavior
       (which may be one of the behaviors in the <a
       href="#animation-of-property-types-">Animation of property
       types</a> section above, or may be a new behavior) to define how
       the property animates.  Such definitions override those given in
       this specification.</p>
       <h3 id="animatable-css"><a id="properties-from-css-">
         Properties from CSS
       </a></h3>
       <p class="issue">Need to define what listing comma-separated
       things here means.  In particular, that they only apply when
       both values fit the type, and that if one of the values is a
       type not listed, or if two of the values are different types,
       then the two values cannot be interpolated.</p>
      <table class="animatable-properties">
        <tr>
          <th>Property Name</th>
          <th>Type</th>
        </tr>
        <tr>
          <td>background-color</td><td>color</tr>
        <tr>
          <td>background-position</td><td>percentage, length</td>
        </tr>
        <tr>
          <td>border-bottom-color</td><td>color</td>
        </tr>
        <tr>
          <td>border-bottom-width</td><td>length</td>
        </tr>
        <tr>
          <td>border-left-color</td><td>color</td>
        </tr>
        <tr>
          <td>border-left-width</td><td>length</td>
        </tr>
        <tr>
          <td>border-right-color</td><td>color</td>
        </tr>
        <tr>
          <td>border-right-width</td><td>length</td>
        </tr>
        <tr>
          <td>border-spacing</td><td>length</td>
        </tr>
        <tr>
          <td>border-top-color</td><td>color</td>
        </tr>
        <tr>
          <td>border-top-width</td><td>length</td>
        </tr>
        <tr>
          <td>bottom</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>clip</td><td>rectangle</td>
        </tr>
        <tr>
          <td>color</td><td>color</td>
        </tr>
        <tr>
          <td>crop <span class="issue">css3-content will likely advance slower than this specification, in which case this definition should move there</span></td><td>rectangle</td>
        </tr>
        <tr>
          <td>font-size</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>font-weight</td><td>font weight</td>
        </tr>
        <tr>
          <td>height</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>left</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>letter-spacing</td><td>length</td>
        </tr>
        <tr>
          <td>line-height</td><td>number, length, percentage</td>
        </tr>
        <tr>
          <td>margin-bottom</td><td>length</td>
        </tr>
        <tr>
          <td>margin-left</td><td>length</td>
        </tr>
        <tr>
          <td>margin-right</td><td>length</td>
        </tr>
        <tr>
          <td>margin-top</td><td>length</td>
        </tr>
        <tr>
          <td>max-height</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>max-width</td><td>length, percentage </td>
        </tr>
        <tr>
          <td>min-height</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>min-width</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>opacity</td><td>number</td>
        </tr>
        <tr>
          <td>outline-color</td><td>color</td>
        </tr>
        <tr>
          <td>outline-offset</td><td>length</td>
        </tr>
        <tr>
          <td>outline-width</td><td>length</td>
        </tr>
        <tr>
          <td>padding-bottom</td><td>length</td>
        </tr>
        <tr>
          <td>padding-left</td><td>length</td>
        </tr>
        <tr>
          <td>padding-right</td><td>length</td>
        </tr>
        <tr>
          <td>padding-top</td><td>length</td>
        </tr>
        <tr>
          <td>right</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>text-indent</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>text-shadow</td><td>shadow</td>
        </tr>
        <tr>
          <td>top</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>vertical-align</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>visibility</td><td>visibility</td>
        </tr>
        <tr>
          <td>width</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>word-spacing</td><td>length, percentage</td>
        </tr>
        <tr>
          <td>z-index</td><td>integer</td>
        </tr>
      </table>
 <p class="issue">
   This list omits the following properties that Gecko can animate, and
   which likely should be included:
   background-size,
   border-*-radius,
   box-shadow,
   column-count,
   column-gap,
   column-rule-color,
   column-rule-width,
   column-width,
   font-size-adjust,
   font-stretch,
   marker-offset,
   text-decoration-color,
   transform,
   transform-origin.
 </p>
      <h3 id="animatable-svg"><a id="properties-from-svg-">
        Properties from SVG
      </a></h3>
      <p>
        All properties defined as animatable in the SVG specification, provided
        they are one of the property types listed above.
       </p>
      <!-- <table>
        <tr>
          <th>Property Name</th><th>Type</th>
        </tr>
        <tr>
          <td>stop-color</td><td>color</td>
        </tr>
        <tr>
          <td>stop-opacity</td><td>float</td>
        </tr>
        <tr>
          <td>fill</td><td>paint server</td>
        </tr>
        <tr>
          <td>fill-opacity</td><td>float</td>
        </tr>
        <tr>
          <td>stroke</td><td>paint server</td>
        </tr>
        <tr>
          <td>stroke-dasharray</td><td>list of numbers</td>
        </tr>
        <tr>
          <td>stroke-dashoffset</td><td>number</td>
        </tr>
        <tr>
          <td>stroke-miterlimit</td><td>number</td>
        </tr>
        <tr>
          <td>stroke-opacity</td><td>float</td>
        </tr>
        <tr>
          <td>stroke-width</td><td>float</td>
        </tr>
        <tr>
          <td>viewport-fill</td><td>color</td>
        </tr>
        <tr>
          <td>viewport-fill-opacity</td><td>color</td>
        </tr>
       </table> -->
 <h2 id="acknowledgments">Acknowledgments</h2>
 <p>Thanks especially to the feedback from
 Tab Atkins,
 Carine Bournez,
 Aryeh Gregor,
 Vincent Hardy,
 Cameron McCormack,
 Alex Mogilevsky,
 and all the rest of the
 <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.</p>
 <h2 id="references">References</h2>
 <h3 class="no-num" id="normative-references">Normative references</h3>
 <!--normative-->
 <h3 class="no-num" id="other-references">Other references</h3>
 <!--informative-->
 <h2 class="no-num" id="property-index">Property index</h2>
 <!-- properties -->
 <h2 class="no-num" id="index">Index</h2>
 <!--index-->
 </body>
 </html>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
 sgml-default-doctype-name:"html"
 sgml-minimize-attributes:t
 End:
 -->

Mercurial > drafts / annotate

css3-transitions/Overview.src.html@6013bb8b5fe9 (annotated)

css3-transitions/Overview.src.html