- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jan 2022 08:44:45 +0000
- To: public-css-archive@w3.org
For reference, the potential conflict arises from this note in the spec.: > Note that order is also important within each animation definition for distinguishing `<keyframes-name>` values from other keywords. When parsing, keywords that are valid for properties other than `animation-name` whose values were not found earlier in the shorthand must be accepted for those properties rather than for `animation-name`. I'd base that decision on statistics of pages currently using the `<single-animation-composition>` keywords as `<keyframe-name>`s. Alternatively, the value for `animation-composition` could be added using a different syntax, e.g. separated via a slash. Though that would probably also be a somewhat arbitrary syntax change. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6930#issuecomment-1005488319 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 January 2022 08:44:47 UTC