You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I got a question about how to integrate view transitions with Mithril, 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.
The text was updated successfully, but these errors were encountered: