- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Apr 2023 18:34:27 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-easing-1] Clarify computed values and serialization == The CSS Easing spec has a [section on serialization](https://www.w3.org/TR/2023/CRD-css-easing-1-20230213/#serialization), however this section doesn't distinguish between specified and computed values (and seems to be defining the computed value serialization). Should there be any differences between these two? E.g. - Should specified values of `step-end` and `step-start` be serialized as themselves rather than as a `steps()` function? - Should the `jump-end` and `end` keywords be kept as distinct specified values? Relatedly, the spec seems a bit confused about the computed/serialized values for `start`/`end`/`jump-start`/`jump-end`: the serializations of the “end” values are collapsed to a single serialization, but not the “start” values. I think - `jump-start`/`jump-end` should compute to `start`/`end` or vice versa (unsure which we prefer). - the computed value serialization should fall out from that Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8723 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 April 2023 18:34:28 UTC