[csswg-drafts] [css-easings-2] Accept `<number> | <percentage>` in `linear()` (#9287)

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-easings-2] Accept `<number> | <percentage>` in `linear()` ==
https://drafts.csswg.org/css-easing-2/#linear-easing-function-syntax

```
<linear-easing-function> = linear(<linear-stop-list>)
<linear-stop-list> = [ <linear-stop> ]#
<linear-stop> = <number> && <linear-stop-length>?
<linear-stop-length> = <percentage>{1,2}
```

What is the reason (if any) to not allow `<percentage>` as the *progress* output of linear easing points?

And vice-versa, what is the reason to not allow `<number>`s as the *time range* start and end input?

Suggested:

```
<linear-easing-function> = linear(<linear-stop-list>)
<linear-stop-list> = <linear-stop>#{2,∞}
<linear-stop> = <linear-stop-point>{1,3}
<linear-stop-point> = <number> | <percentage>
```

Or (borrowing gradient's syntax in CSS Images 4):

```
<linear-easing-function> = linear(<linear-stop-list>)
<linear-stop-list> = <linear-stop>#{2,∞}
<linear-stop> = <linear-stop-progress> && <linear-stop-hint>
<linear-stop-progress> = <number> | <percentage>
<linear-stop-hint> = [<number> | <percentage>]{1,2}
```

---

*aside*

I think the target `<number>` range to resolve `<percentage>` should be explicitly defined, like with the `Percent reference range` of color functions in CSS Color 4.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9287 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 1 September 2023 06:30:08 UTC