- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Feb 2022 21:31:15 +0000
- To: public-css-archive@w3.org
Yes, but not the update I wanted. The use-counter is [at almost 4%](https://chromestatus.com/metrics/feature/timeline/popularity/4066), which is _way_ higher than expected. I've been waiting for sample pages to come in so I could check if there's any typical usage patterns we could use to argue that the change doesn't matter, but at 4% it might be futile to find the "typical" usage patterns anyway. So as it stands, the use-counter did not help in making a confident decision here, unfortunately. @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? -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6688#issuecomment-1043468719 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 February 2022 21:31:17 UTC