compositing: Move image output and shutdown management out of the compositor #50836
+1
−0
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
.access the image contents of a
WebView
viaRenderingContext::read_to_image
. Most options for this are moved toServoShellPreferences
apart fromwait_for_stable_image
as thisrequires a specific kind of coordination in the
ScriptThread
that isalso very expensive. Instead, paint is now simply delayed until a
stable image is reached and
WebView::paint()
returns a boolean.Maybe this can be revisited in the future.
is shared between the compositor and
Servo
instance. In the future,this sharing might be unecessary.
This change also allows saving others types of image output just as JPEG.
Co-authored-by: Ngo Iok Ui (Wu Yu Wei) [email protected]
Signed-off-by: Martin Robinson [email protected]
Reviewed in servo/servo#35538