- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Oct 2022 09:24:30 +0000
- To: public-css-archive@w3.org
> Going further, maybe we should disallow reordering the values? There is precedent to have the `*-name` first: the `container` shorthand has the `container-name` first and then the container-type. `animation` has `animation-name` last (conflict with `animation-fill-mode` for `none`). --- > See also #7694 (which doesn't address the ordering, but it's related). I presume that the topic related to this PR is about whether `none` can repeat. Some context: `none` can repeat in `animation` for `animation-name` but it cannot in `transition` for `transition-property` (there is a minor [issue](https://github.com/w3c/csswg-drafts/issues/2031) related to how this is enforced). The current `view-timeline-name` syntax does not allow repeating `none` but the current `view-timeline` syntax does. There is also: > If `view-timeline-name` has more names than `view-timeline-axis` has specified axes, the excess timelines use the last `view-timeline-axis` value. If `view-timeline-name` has fewer names than view-timeline-axis has specified axes, the used view-timeline-axis list is truncated. If this difference is unintentional and `none` should not repeat in `view-timeline` AND `view-timeline-name`, it seems simpler and clearer to enforce it in prose rather than in the syntax (cf. my suggestion in the linked issue related to `transition`). -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7627#issuecomment-1280553623 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 October 2022 09:24:32 UTC