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

Those are neat diagrams and the effects you've produced look great. They seem to cover the different use cases well.

As someone who is not very familiar with gradients (I need to look it up every time) I don't find the parallel with gradient syntax particularly helpful. In particular, putting the "y" value (`<cubic-spline-knot-position>`) before the "x" offset (`<cubic-spline-knot-time>`) feels back-to-front compared to how I'm used to thinking with regards to keyframe offsets. However, that may be just me, and given that these easing functions may be used with gradients, aligning the syntax probably makes sense.

Currently all easing functions go from (0,0) to (1,1). I'm unsure if we should break that invariant or not (as this syntax currently allows). I seem to recall it had unfortunate implications in the realm of `GroupEffect`s (where timing functions are effectively layered on top of one another) but perhaps it's ok.

-- 
GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/229#issuecomment-491646123 using your GitHub account

Received on Monday, 13 May 2019 01:12:03 UTC