Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify serialization for timing functions #340

Merged
merged 2 commits into from
Jul 26, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions css-transitions/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -445,6 +445,26 @@ Introduction {#introduction}
</dd>
</dl>

### Serializing a timing function ### {#serializing-a-timing-function}

Timing functions are serialized using the common serialization patterns
defined in [[CSSOM]] with the following additional requirements:

* The keyword values ''ease'', ''linear'', ''ease-in'', ''ease-out'',
and ''ease-in-out'' are serialized as-is, that is, they are
<em>not</em> converted to the equivalent ''cubic-bezier()''
function before serializing.

* Step timing functions, whether they are specified using the
''steps()'' function or either of the ''step-start'' or ''step-end''
keywords, are serialized as follows:

1. If the point at which the value changes is ''end'', serialize
as <a lt="steps()" function>steps(&lt;integer&gt;)</a>.

2. Otherwise, serialize as <a lt="steps()"
function>steps(&lt;integer&gt;, start)</a>.

<span id="the-transition-delay-property-">The 'transition-delay' Property</span> {#transition-delay-property}
-------------------------------------------------------------------------------------------------------------

Expand Down