- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Sep 2017 23:36:52 +0000
- To: public-css-archive@w3.org
My guess here is that Edge and Chrome run these event handlers synchronously instead of batching them. CSS Transitions 2 makes it more obvious that they should be batched, but even then it's not entirely clear. I think we need to tidy up HTML's processing model so that the step that refers to running CSS and dispatching events actual includes sending CSS animation events, CSS transition events, and Web Animations' animation playback events. (See https://github.com/whatwg/html/issues/707). These events should ideally be batched and sorted. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1820#issuecomment-330385845 using your GitHub account
Received on Monday, 18 September 2017 23:36:45 UTC