- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Feb 2022 01:52:00 +0000
- To: public-css-archive@w3.org
> @birtles In light of this, do you think we should do the following? > > > We could explicitly specify in https://drafts.csswg.org/css-transitions-1/#starting that a transition should not start if there's currently an animation on the same property. I don't think that behavior must arise from the current definition of before/after-change style? I think so. Transition events are quite important to a lot of apps -- often various state changes are keyed off getting a `transitionend` event. I think any change to the circumstances under which transition events are dispatched is risky and we should try to match the current (interoperable) behavior there. (Anecdotally, many many years ago when working on Firefox OS, a recurring cause for apps breaking was that they didn't receive expected `transitionend` events which is what motivated specifying the `transitioncancel` event.) -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6688#issuecomment-1043722187 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 February 2022 01:52:02 UTC