W3C home > Mailing lists > Public > www-style@w3.org > December 2017

[CSSWG][css-timing] FPWD of CSS Timing Functions (late announce)

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 25 Dec 2017 13:30:52 +0330
To: "www-style@w3.org" <www-style@w3.org>, "public-fx@w3.org" <public-fx@w3.org>, www-svg <www-svg@w3.org>, public-review-announce@w3.org
Message-ID: <5dbd035b-4b17-a8b3-9a1b-c94cb2d19287@inkedblade.net>
Seem to be missing this announcement as well...
On 21 February 2017, the CSS WG published a First Public Working Draft of the
CSS Timing Functions Module Level 1

     https://www.w3.org/TR/css-timing-1/

This module extracts the various timing functions in CSS Transitions [1] into
their own module, for easier re-use across modules.

It also adds a new stepped timing notation for looped animations (called
frames() in the FPWD, but to be changed to an extension of steps() [2]).

[1] https://www.w3.org/TR/2013/WD-css3-transitions-20131119/
[2] https://www.w3.org/mid/CADhPm3tGT-NmA57Rne5W60FxVbY1wV6xBrMNtBm0zKXs7MOpZg@mail.gmail.com

There was a request to change the name of the module to be more general
for potential re-use with progressions other than time, such as in gradients;
therefore, unless someone comes up with a much better idea soon, it is
expected that the next publication will be titled CSS Easing Functions
[css-easing].

Please review the draft, and send any comments to this mailing list,
<www-style@w3.org>, prefixed with [css-timing] (as I did on this
message) or (preferably) file them in the GitHub repository at
   https://github.com/w3c/csswg-drafts/issues

For the CSS WG,
~fantasai
Received on Monday, 25 December 2017 12:43:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 December 2017 12:43:10 UTC