Renderer-Compositor Data Exchange for View Transitions

These sources detail the internal data pipeline in Chromium used to coordinate View Transitions between the renderer’s main thread and the compositor thread. The process begins on the main thread, where Blink generates requests that are moved through the commit boundary into the compositor’s tree. Once on the compositor thread, these requests are converted into directives for the Viz service or serialized via Mojo in specific rendering modes. A crucial feedback loop exists where the compositor sends computed element coordinates back to the main thread to trigger completion callbacks. The documentation also covers latency-reducing features like early acknowledgments and the use of GPU shared images for snapshotting. Overall, the text serves as a technical overview of the synchronization and resource plumbing required for smooth visual transitions.