Re: [csswg-drafts] [css-transitions] starting an animation and a transition with equal values yields some incompatible behavior between Safari, Chrome and Firefox (#8701)

Strictly literally following the spec text for [starting of transitions](https://www.w3.org/TR/css-transitions-1/#starting), I believe a transition is expected to start. In particular, the after-change style explicitly uses the computed values of the `animation-*` properties from the before-change style which don't have the new animation.

However, I don't think this is ideal behavior. If the animation were started slightly earlier than the underlying style change the transition wouldn't have started. Also, the canceling and restarting of transitions due to a running of an animation feels like a degenerate behavior resulting from this. Further, the transition is entirely covered up by the animation. I think if an animation will be active and replace the property value (i.e. with the default composite mode `replace`) that we shouldn't start a transition.

-- 
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8701#issuecomment-1503620359 using your GitHub account


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

Received on Tuesday, 11 April 2023 15:31:20 UTC