[csswg-drafts] [css-transitions] (#8761)

dholbert has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-transitions]  ==
I have a clarity/correctness nit with this spec text that was recently added to css-transitions-2.

Spec link:
https://drafts.csswg.org/css-transitions-2/#transition-property-property

Specifically this block of text:
https://github.com/w3c/csswg-drafts/commit/69f4ac71c0ae0ae70e363c775c1f84e87d3935ff#diff-a9fb88c817f0afdb3cb3e08c28315c1174ef4e5d7db3e09c7dffe49a4a5a59dbR87-R91

I'll quote the text in question (emphasis added):
> In CSS Transitions Level 2, property **values** are transitionable unless **they have an [animation type](https://w3c.github.io/csswg-drafts/web-animations-1/#animation-type)** that is [not animatable](https://w3c.github.io/csswg-drafts/web-animations-1/#not-animatable). **Values with a [discrete](https://w3c.github.io/csswg-drafts/web-animations-1/#discrete) animation type** are transitionable, and flip at 50% progress (p = 0.5).

ISSUE:
This spec text is written as if **values themselves** might be transitionable-or-not, and as if they might have particular value-specific "animation type" (of "not animatable" or "discrete").

This doesn't quite make sense -- the "animation type" concept is associated with a CSS **Property** rather than with its values, as defined at https://drafts.csswg.org/web-animations-1/#animation-type (particularly in the case of the "not animatable" animation type).

SUGGESTED FIX:
@fantasai I think this paragraph should be rewritten to talk about the **properties** being transitionable and having a particular "animation type", rather than the values -- does that make sense? Or if there's value-specific subtlety that we're trying to lean into here, we should perhaps make that more apparent.

(Note that the immediate next paragraph talks about "transitionable properties" so I think that is the meaning we're going for.)

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8761 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 24 April 2023 18:33:37 UTC