- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Feb 2023 05:11:39 +0000
- To: public-css-archive@w3.org
Good question. I don't recall, but I suspect this came about because when CSS transitions etc. were introduced, we didn't want to have to edit all the specs in order to mark all the properties as animatable. Rather, we just defined, e.g. how to animate a `<length>` and if the property took a `<length>` it would animate using that definition unless it explicitly opted out of it. If we're now at the point where all the specs have `Animatable type` specified, then we _could_ switch that definition to default to not animatable as suggested. Personally, I think the cases where we _don't_ want a property to be animatable are very few (e.g. `animation-*` properties and possibly `display`) such that they are very much the exception and require justification for why they are _not_ animatable so keeping animatable as the default makes sense to me in that regard. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8428#issuecomment-1423645368 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 February 2023 05:11:41 UTC