- From: Claudia Meadows via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Apr 2025 05:34:59 +0000
- To: public-css-archive@w3.org
dead-claudia has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-1] How should view transitions be wired up in frame-timed update loops? == [I got a question about how to integrate view transitions with Mithril](https://github.com/MithrilJS/mithril.js/discussions/3014), and it's very awkward to integrate. In fact, in the face of frame-timed updates, it ends up actively causing glitchiness, and that very thread ran into such a real-world integration problem. Mithril, like many frameworks, batches its DOM updates to run all at once within animation frame callbacks for performance. One of the cause of problems I suspect is exactly that animation frame batching. Microtasks scheduled within renders are delayed until after the DOM is consumed for paint. And I could see this causing timing delays and other glitches during update. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12125 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 26 April 2025 05:35:00 UTC