(In reply to David Shin[:dshin] from comment #5) > The root cause seems to be that we are ending up animating `display` here. It's [not animatable](https://drafts.csswg.org/css-display/#the-display-properties). In fact, replacing `--disp` with `display` result in a static purple div across the 3 browsers. > > Overall, this seems like a side-effect of animatable custom properties being applied to display. Right. `display` property is not ready to be discrete animatable, so in this case it accidentally generates a discrete animation there. We may have to prevent it from creating any animations on the non-animatable properties when using custom variables.
Bug 1941651 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to David Shin[:dshin] from comment #5) > The root cause seems to be that we are ending up animating `display` here. It's [not animatable](https://drafts.csswg.org/css-display/#the-display-properties). In fact, replacing `--disp` with `display` result in a static purple div across the 3 browsers. > > Overall, this seems like a side-effect of animatable custom properties being applied to display. Right. `display` property is not ready to be discrete animatable, so in this case it accidentally runs a discrete animation there I guess. We may have to prevent it from running any animations on the non-animatable properties when using custom variables.