[css-transition] Does transition-property: all
really need special handling?
#8024
Labels
css-transitions-1
Current Work
https://drafts.csswg.org/css-transitions-1/#transition-property-property
I think it's not obvious why
<single-transition-property> = all | <custom-ident>
with some special behavior forall
instead of treatingall
as a generic shorthand.If I get it right, the difference is that the
all
value affects the properties not included in theall
shorthand, i.e.direction
,unicode-bidi
and custom properties.The difference doesn't typically matter since
direction
,unicode-bidi
are not animatable, and unregistered custom properties animate discretely. So it only matters for registered custom properties, right? I think this deserves a note.But in fact, was this deliberate? Initially the
all
value was not allowed to appear in the list, likenone
, so that's why it needed special handling. 6d0e135 allowed it in the list of idents. This happened in Feb 2012 after a resolution in Nov 2011. But at that point,all
was defined to include all properties:unicode-bidi
anddirection
, this didn't change until Jul 2013.all
wasn't noticed/addressed until Aug 2018So it seems to me that at that time, the special behavior for the
all
value was identical to the behavior that we would get by treating it as a reference to the shorthandall
. But things changed, possibly without noticing the effect ontransition-property
.I'm not a big fan of this special behavior for
all
. I wonder if we can:all
, just treat it as other shorthands. This would only impact registered custom properties.--
to refer to all custom properties.everything
(or whatever ident that does not exist as a property) to refer to all properties (i.e. the current behavior of theall
value).I think compatibility may not be a problem since:
all
stops transitioning registered custom properties, the standard properties that use the custom properties will still transition, so in simple cases the outcome will be the same.The text was updated successfully, but these errors were encountered: