W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

Re: [csswg-drafts] [css-easing-2] Complex easing/timing functions (#229)

From: VisibleCode via GitHub <sysbot+gh@w3.org>
Date: Tue, 30 Apr 2019 07:46:39 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-487850536-1556610397-sysbot+gh@w3.org>
> We'd also want to make it possible to convert from software that currently uses path notation, like Greensock. Which, based on my testing with their visualizer, seems to use the rule proposed by @SebastianZ to convert arbitrary paths into functions.

What Greensock does is discard the parts of the path between where x starts decreasing to where it catches up again. I don't know the details of the implementation, but bezier path intersections tend to have rough edge cases to account for.

Obviously any reasonable easing representation should be able to support export _after_ pruning. But should browsers be expected to implement on-the-fly pruning themselves?

GitHub Notification of comment by visiblecode
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/229#issuecomment-487850536 using your GitHub account
Received on Tuesday, 30 April 2019 07:46:40 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC