| Summary: | [css-easing-2] Implement linear(...) easing function for css animations | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Tim Nguyen (:ntim) <ntim> |
| Component: | Animations | Assignee: | Devin Rousso <hi> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | augus.dupin, cyb.ai.815, dino, graouts, graouts, jaffathecake, joris.bruijnzeels, safari-dev, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 14 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugzilla.mozilla.org/show_bug.cgi?id=1764126 https://github.com/w3c/csswg-drafts/pull/6533 https://bugs.webkit.org/show_bug.cgi?id=260136 |
||
|
Description
Tim Nguyen (:ntim)
2022-05-04 03:32:23 PDT
I've pushed the spec for this https://drafts.csswg.org/css-easing-2/#the-linear-easing-function. Pull request: https://github.com/WebKit/WebKit/pull/15936 Committed 266195@main (2b0ebfa3b59e): <https://commits.webkit.org/266195@main> Reviewed commits have been landed. Closing PR #15936 and removing active labels. I expect the changes made in 266196@main are not dealing with accelerated animations. Indeed, CoreAnimation doesn’t have any native equivalent to linear() so we’ll have to either find something that matches and add code to translate to the CA-native primitive or expand KeyframeEffect::canBeAccelerated() to do something similar to what we do with steps(). I argue for the latter because with the work for threaded animation resolution support for linear() will be free and I think it’s not a good idea to add more CA-specific code. Filed bug 260136. |