- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Aug 2024 00:05:19 +0000
- To: public-css-archive@w3.org
svgeesus has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-easing] `linear` keyword is described as a function in level 1, inconsistent with level 2 == CSS Easing 2 defines [2.2. The linear easing **keyword**: `linear`](https://drafts.csswg.org/css-easing-2/#valdef-easing-function-linear)] as a [linear easing function](https://drafts.csswg.org/css-easing-2/#linear-easing-function) with two points, [0,0] and [1.1]. It also fully defines the [linear easing **function** `linear()`](https://drafts.csswg.org/css-easing-2/#the-linear-easing-function), with syntax, serialization, etc. CSS Easing 1 briefly defines [2.1. The linear easing function: `linear`](https://drafts.csswg.org/css-easing-1/#valdef-easing-function-linear) but describes it as a function (despite the lack of `()`), and then later on says that it is "simply the `linear` keyword". I guess the definition in CSS Easing 1 is an earlier attempt, but now that the definition in CSS Easing 2 is well developed it seems that CSS Easing 1 should be aligned with it. I can see two ways: 1. Define it as a keyword, which it is, but without reference to an undefined (in that level) linear easing function 2. Remove the definition, and just let CSS Easing 2 fully define it. @birtles @grorg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10734 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 August 2024 00:05:20 UTC