compositing: Move image output and shutdown management out of the compositor #50893
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a step toward the renderer-per-WebView goal. It moves various details out of
IOCompositor
.WebView
viaRenderingContext::read_to_image
. Most options for this are moved toServoShellPreferences
apart fromwait_for_stable_image
as this requires a specific kind of coordination in theScriptThread
that is also very expensive. Instead, paint is now simply delayed until a stable image is reached andWebView::paint()
returns a boolean. Maybe this can be revisited in the future.Servo
instance. In the future, this sharing might be unecessary.CompositeTarget
has been removed entirely. This no longer needs to be passed when creating a Servo instance.This is an attempt to land #50836 which seems to be wedged.
Reviewed in servo/servo#35538