- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Dec 2022 21:59:41 +0000
- To: public-css-archive@w3.org
@flackr Thanks for taking this. Looks reasonable overall, I left some comments. I assume we're pretending that other troublemakers (css-toggle, css-anchor, container queries) don't exist at the moment. Ultimately we'll need to know the order of various passes. > Note that unlike your proposal, JS constructed animations still sample at the beginning of the frame. I feel like trying to defer script constructed animations adds unnecessary complexity - though it does mean that we have to freshen style and layout additionally during step 7.10 for those animations but I believe we already have to do this for event dispatch. I disagree, I think it's eagerly doing style and layout in the lifecycle that adds unnecessary complexity. Even what Blink is currently doing for JS constructed timelines seems preferable. > If we want to defer them we'll have to track newly constructed timelines beyond the scope of one event loop update. That seems entirely doable for both spec and implementation. :-) -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5261#issuecomment-1338230652 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 December 2022 21:59:43 UTC