- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Jun 2024 01:49:19 +0000
- To: public-css-archive@w3.org
> That’s highly unlikely, since, as explained many times before, different use cases require different color interpolation settings. My apologies, I haven't seen that context. I had a think about this and I'm afraid I don't think `-behavior` is the correct approach here. The main issue is a layering one. `transition-behavior` affects what animations get generated in the first place. As a result, it doesn't really make sense to map it to a property on a generated animation. It answers the question of "What animations get generated?", not "How do they behave?". We _could_ still add a `behavior` property to animations with a default value of `allow-discrete` and then define that animations ignore any discrete properties listed in their keyframes (or subproperties of shorthands listed in their keyframes) but it wouldn't really be doing that same thing as `transition-behavior` which simply prevents animations from being generated in the first place. Furthermore, it would complicate using the `behavior` property since authors would need to be sure to preserve the initial `allow-discrete` value when specifying additional interpolation options. Personally I think adding a very generic sounding `behavior` property to the API would also be unfortunate when something like `interpolation` would be more intuitive to both read and write. All said, I think Lea's original suggestion of adding a separate animation interpolation properties (#7035) is preferable here and `transition-behavior` should remain something specific to which transitions are generated. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7063#issuecomment-2185438388 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 June 2024 01:49:20 UTC