- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Apr 2023 02:04:41 +0000
- To: public-css-archive@w3.org
> * Should specified values of `step-end` and `step-start` be serialized as themselves rather than as a `steps()` function? In general it's easier for authors if they don't need to write parsers for multiple potential outputs and can always assume a certain format. That said, Chrome appears not to support that: https://wpt.fyi/results/css/css-easing/step-timing-functions-syntax.html?label=experimental&label=master&aligned > * Should the `jump-end` and `end` keywords be kept as distinct specified values? Yes. We'd _like_ to normalize to `jump-end` but in the interests of Web compat, we shouldn't unless we have data to indicate it's safe to do so. > the serializations of the “end” values are collapsed to a single serialization, but not the “start” values. That's intentional. We'd like to use `jump-*` values everywhere but we can't because of Web compat. The only case where we can is `end` / `jump-end` because it happens to be the default value so, according to standard CSS serialization rules, we omit it. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8723#issuecomment-1509466642 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 April 2023 02:04:43 UTC