The compositor is moving into a dedicated helper process. That requires a process to launch, channels for Browser and WebContent to talk to it over, and client proxies on each side. Land all of that as an inert scaffold first, gated behind --enable-compositor-process, so the default rendering path is unchanged and later commits can fill in the protocol, the service-side state, and the runtime switch against a stable target.
4 lines
99 B
Text
4 lines
99 B
Text
endpoint CompositorControlClient
|
|
{
|
|
did_connect_web_content(i32 web_content_connection_id) =|
|
|
}
|