- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Jun 2023 14:02:47 +0000
- To: public-css-archive@w3.org
Proposed resolution: Go with option 2 above, adding a transition longhand for specifying whether the transition should allow discrete interpolation. This will follow the [same convention as the other transition longhands where the list is repeated if shorter than the transition-property list](https://drafts.csswg.org/css-transitions/#transition-duration-property:~:text=the%20user%20agent%20must%20calculate%20its%20used%20value%20by%20repeating%20the%20list%20of%20values%20until%20there%20are%20enough). Given this is in reference to the [animation-type](https://www.w3.org/TR/web-animations/#animation-type)) it's probably worth sharing some of the terminology. Possible property names: * `transition-mode` * `transition-type` * `transition-animation-type` Possible property values: * For referring to interpolable transitions we could use `normal` (as it's the pre-existing mode), or `interpolable` explaining that it is anything animatable and not discrete. * For referring to including discrete transitions, we could say `discrete` to refer to the specific animation type, or `animatable` as the intention would be that we animate anything that is animatable. I think my preference would be `transition-type: <normal | animatable>#`. Using animatable rather than discrete because it matches exactly the spec terminology for what will be transitioned - anything that can be animated. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8857#issuecomment-1580890102 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 June 2023 14:02:48 UTC