Intent to Implement: Support step timing functions jump-start|end|both|none

65 views
Skip to first unread message

Kevin Ellis

unread,
May 30, 2019, 2:25:07 PM5/30/19
to blink-dev
kev...@chromium.org https://danielcwilson.com/blog/2019/02/step-and-jump/ https://developer.mozilla.org/en-US/docs/Web/CSS/animation-timing-function Specification: https://drafts.csswg.org/css-easing-1/#step-easing-functions The step timing functions jump-both, jump-none, jump-start and jump-end were introduced to the spec for easing functions in 2018. Two of these (jump-start and jump-end) are aliases for start and end, respective. The remaining 2 provide increased flexibility for step transitions by enabling step functions in which both or neither endpoint has a discontinuous step. Previously, one and only one of the two endpoints could have a step discontinuity. Provided support for a richer set of step animations. Firefox already has support for jump-* step timing functions. Adding support in Blink improves cross-browser interoperability.
The jump-* step timing functions are already supported in Firefox. Firefox: Shipped (https://wpt.fyi/results/css/css-easing/step-timing-functions-syntax.html) Edge: No public signals Safari: No public signals Web developers: No signals
Yes Yes Existing WPT tests for parsing, serialization and output of jump-* step timing functions. https://www.chromestatus.com/features/5730327525851136

kev...@google.com

unread,
May 31, 2019, 9:44:21 AM5/31/19
to blink-dev
Title should have read "Intent to Implement and Ship: ...".  

Yoav Weiss

unread,
May 31, 2019, 11:59:20 AM5/31/19
to Kevin Ellis, blink-dev
Has this been reviewed by the TAG? 
 
The step timing functions jump-both, jump-none, jump-start and jump-end were introduced to the spec for easing functions in 2018. Two of these (jump-start and jump-end) are aliases for start and end, respective. The remaining 2 provide increased flexibility for step transitions by enabling step functions in which both or neither endpoint has a discontinuous step. Previously, one and only one of the two endpoints could have a step discontinuity. Provided support for a richer set of step animations. Firefox already has support for jump-* step timing functions. Adding support in Blink improves cross-browser interoperability.
The jump-* step timing functions are already supported in Firefox. Firefox: Shipped (https://wpt.fyi/results/css/css-easing/step-timing-functions-syntax.html) Edge: No public signals Safari: No public signals

Have we tried to gather signals from Safari folks?
 
Web developers: No signals
Yes Yes Existing WPT tests for parsing, serialization and output of jump-* step timing functions. https://www.chromestatus.com/features/5730327525851136

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAE1FVET5UUOkbhfiNEQHCUi_zX8RoWz5_Sy238dppiTJRd2jSA%40mail.gmail.com.

Stephen Mcgruer

unread,
May 31, 2019, 1:33:28 PM5/31/19
to Yoav Weiss, Kevin Ellis, blink-dev
Has this been reviewed by the TAG? 

css-easing-1 was reviewed a long time ago when it was called css-timing-1 in https://github.com/w3ctag/design-reviews/issues/161. The only recommendation (the final status is unclear, the issue was closed without comment) was to rename the frames() timing function, which was done in https://github.com/w3c/csswg-drafts/issues/1680 and ultimately resulted in the introduction of the jump-* notation in https://github.com/w3c/csswg-drafts/commit/9bc2f6e4b8a641e297e2a1e920638f08cba7e415

kev...@google.com

unread,
May 31, 2019, 1:41:30 PM5/31/19
to blink-dev, kev...@chromium.org
Safari tracking bug: https://bugs.webkit.org/show_bug.cgi?id=190406

WPT tests using jump-both or jump-none are failing on Safari 82 preview.


To unsubscribe from this group and stop receiving emails from it, send an email to blin...@chromium.org.

Stephen Mcgruer

unread,
Jun 5, 2019, 10:49:49 AM6/5/19
to Kevin Ellis, blink-dev, Kevin Ellis
Ping, bcc blink-api-ow...@chromium.org for attention ;). Please note when reviewing that this is an I2I&S, see the first reply from kevers@

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f3ebe274-83ce-4ae2-85a5-4da56e756dd3%40chromium.org.

Daniel Bratell

unread,
Jun 5, 2019, 11:24:29 AM6/5/19
to Kevin Ellis, Stephen Mcgruer, blink-dev, Kevin Ellis
LGTM1 for Intent to Implement & Ship.

I wonder what we can do to make the expectatins on the TAG part clearer so that we don't have to do this back-forth to clarify it so often.

/Daniel
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CADY3MaeJQN3itNy1w_fMYJd1qE%2BmzfHsKt8X%2Bzkqqq9GQJTs-A%40mail.gmail.com.



--
/* Opera Software, Linköping, Sweden: CEST (UTC+2) */

Yoav Weiss

unread,
Jun 6, 2019, 5:19:23 AM6/6/19
to Daniel Bratell, Kevin Ellis, Stephen Mcgruer, blink-dev, Kevin Ellis

Chris Harrelson

unread,
Jun 6, 2019, 10:16:00 AM6/6/19
to Yoav Weiss, Daniel Bratell, Kevin Ellis, Stephen Mcgruer, blink-dev, Kevin Ellis
Reply all
Reply to author
Forward
0 new messages