- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Apr 2023 15:29:47 +0000
- To: public-css-archive@w3.org
It does seem simpler than having extra serialization complexity / oddness for the shorthand due to: [the first value in each <single-animation> that can be parsed as a <time> is assigned to the 'animation-duration'](https://www.w3.org/TR/css-animations-1/#animation:~:text=the%20first%20value%20in%20each%20%3Csingle%2Danimation%3E%20that%20can%20be%20parsed%20as%20a%20%3Ctime%3E%20is%20assigned). > I am more concerned about this being the only property that currently takes an auto keyword, and it claiming that keyword in the shorthand for the future Restating to make sure I understand, the problem is if we want to allow auto for some of the other longhands we wouldn't be able to make them accept `auto` before `animation-duration` in the shorthand. This wouldn't be a problem for anything that accepts times as they already are assigned in order, but could be problematic for any of the non-time properties. It would be nice to come up with some general way to handle this, e.g. `animation-duration: auto` becoming `auto-duration` or some other unique keyword. That said, these time-accepting properties are the only current form of measurement/length in the animation property. I think there's precedent in other shorthands, e.g. `background` accepts `auto` as the `background-size` preventing `auto` from being accepted for any other background longhands. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8656#issuecomment-1518002637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 April 2023 15:29:49 UTC