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: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Sat, 21 Aug 2021 18:09:12 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-903154667-1629569350-sysbot+gh@w3.org>
Yeah like I said, *all* numbers can be percentages, *especially* when they're typically in the [0,1] range.

But we have precedence that progress is written as a % (from both animations and gradients), and forcing it to be a % while the other is a number gives us useful readability benefits, whereas making them both the same type (or allowing both to be either type) makes it *harder* to read.

> I don't have a gut feeling for what "expected" behaviour is here, but if folks expect flat at the start/end maybe we should make that the default.

Problem is that if we do that, then we still need to add a *separate* mechanism to make it extendable so you can get the same behavior as `linear`. Out-of-bounds progress is mostly a corner-case anyway; unless there's a great reason to do one or other specifically, I'd prefer we go with the behavior that gives us the simplest syntax. (Which means, currently, I prefer "extend the first/last segment indefinitely, and you can get flat manually without much effort by just making the first/last segment flat".)

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 21 August 2021 18:09:14 UTC

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