- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Jun 2024 13:35:40 +0000
- To: public-css-archive@w3.org
@birtles I get the distinction you’re drawing, but I worry it’s largely philosophical and not evident in the naming of `transition-behavior`, so in practice it will just confuse authors (_which property was it that I use for that flag? `transition-behavior` or `transition-interpolation`?) If anything, `-behavior` seems more fitting for what we're discussing here than for `allow-discrete`. I wonder if we can change the name of `transition-behavior` or if it’s too late. We could do some compat analysis and check that out. > 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. Oh absolutely, that would be terrible ergonomics. It’s also unclear whether there are use cases for _disabling_ discrete animations. If we were to go that route, I suspect `allow-discrete` would be on anyway, and either it would not be an allowable value, or for consistency you _could_ specify it explicitly if you wanted, but it would not make a difference. Having to specify `allow-discrete` every time you set a color interpolation space is absolutely dreadful DX, and I was never proposing that. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7063#issuecomment-2186601334 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 13:35:41 UTC