Re: [csswg-drafts] [css-view-transitions-1] How should view transitions be wired up in frame-timed update loops? (#12125)

Okay, I have a proposal:

- Add a `controlled: true` option to the view transaction factory to start it suspended and delegate update scheduling control to the caller.
- Add a `transaction.beginCapture()` method to begin DOM update capture. Frameworks and their users would call this upon entering new routes and such.
    - This mirrors the calling of the update callback.
- Add a `transaction.endCapture()` method to end DOM update capture and enable animations to start. Frameworks and their users would call this after layout completes.
    - This mirrors the resolution or rejection of the update callback.

Frameworks need a single owner of update scheduling. They can't deal with browsers owning some and the framework owning others without significant changes. My proposal removes the scheduling aspect to ease use with frameworks.

-- 
GitHub Notification of comment by dead-claudia
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12125#issuecomment-2843226138 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 30 April 2025 20:39:22 UTC