Also updates the browser-side UnboundedSurfaceWindow implementation to
allocate dummy Mojo remote/receiver connections to keep the Viz-side
CompositorFrameSinkImpl connection alive, preventing premature
self-destruction.This was a Jetski thing, which seems hacky, but I'm not sure if there's a better way to keep the connection alive?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
cc looks fine, but looping in more folks for trees in viz review.
Is it correct to say that we have a layer in the "main" compositor frame sink support that internally finds and binds to the unbounded compositor frame sink support? Or how does that work?
+vasilyt +zork for trees in viz review, feel free to redirect as appropriate.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
cc looks fine, but looping in more folks for trees in viz review.
Is it correct to say that we have a layer in the "main" compositor frame sink support that internally finds and binds to the unbounded compositor frame sink support? Or how does that work?
+vasilyt +zork for trees in viz review, feel free to redirect as appropriate.
Roughly yes I think that's exactly right. Before, the browser handling connecting the Viz process with the renderer, so that the renderer could send things to the right sinks, separately. Now (with treesinviz), since the layer tree is already in Viz, it doesn't have to cross Mojo boundaries to find the unbounded element's sink. It just needs the ID and it can look it up locally. Otherwise, the logic stays the same.
Thanks for adding more reviewers, who can tell me I'm wrong. 😊
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Gentle ping zork@ and vasilyt@.
Also +rakina@ for content/browser/*.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |