W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2021

Re: [csswg-drafts] [css-easing-1] Some ideas for linear() easing (#6533)

From: Jake Archibald via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 Aug 2021 08:15:40 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-903545233-1629706539-sysbot+gh@w3.org>
I've updated the initial comment to reflect feedback. I've changed the spec to follow, and made it less algorithmic as @tabatkins suggested. I hope it still makes sense! I guess it would benefit from diagrams like I've included in the OP.

> * Speaking of which, does the spec need to define how the second `<<number>>` is calculated when not specified? And the serialization of the function?

Yes, I'm not really sure how to write that down, but we need something that converts the notation into a set of points. Also, `calculate linear output progress` needs connected up so it's actually used.

I tried to copy the syntax from `linear-gradient`, but I couldn't see where things like `yellow 40% 60%` are allowed. I'm looking at [the syntax](https://drafts.csswg.org/css-images-3/#typedef-color-stop-list), but I can't see how it allows three values

> Secondly, an even more pedantic point just to get this out of the way, @fantasai once taught me that it's helpful to break up lines quite a bit, roughly one line per clause so that it makes it easier to follow the blame log later.

I've given this a go (although I generally find it more of an authoring burden vs any later benefit). However, it isn't the style used throughout the rest of the document.

GitHub Notification of comment by jakearchibald
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6533#issuecomment-903545233 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 August 2021 08:15:42 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:48 UTC