- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jul 2022 08:29:22 +0000
- To: public-css-archive@w3.org
@tabatkins @birtles In terms of serialization, I think the normative text is correct. > * The keyword values ''ease'', ''linear'', ''ease-in'', ''ease-out'', and ''ease-in-out'' are serialized as-is, that is, they are _not_ converted to the equivalent ''cubic-bezier()'' or ''linear()'' function before serializing. > > * Step easing functions, whether they are specified using the ''steps()'' function or either of the ''step-start'' or ''step-end'' keywords, are serialized as follows: > > 1. If the [=step position=] is ''jump-end'' or ''end'', serialize as steps(<integer>). > > 2. Otherwise, serialize as steps(<integer>, <step-position>). > > * A linear easing function created via ''linear()'' is serialized by getting its serialized computed value. It explicitly says that `linear` should serialize as-is, and not be converted to the equivalent `linear()` function. Only functions created via `linear()` are serialised to the function form. So: - `linear` serializes as `linear` - `linear(0, 1)` serializes as `linear(0 0%, 1 100%)` I think that's the behaviour we're agreeing on, so I guess the note is misleading? -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/7484#issuecomment-1181474460 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 July 2022 08:29:24 UTC