libservo: Have WebView take a RenderingContext rather than Servo
#40794
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 the last major change before we can try to implement support for
multiple windows in Servo. This change makes it so that each
WebView(via
WebViewBuilder) takes theRenderingContextas an argument,rather than
Servo(viaServoBuilder) as a whole.In the compositor, when registering the
RenderingContext, if aPainteris found for it, it is returned. Otherwise, a newPainter(and WebRender instance) is created for it. There is currently no way to
unregister a
RenderingContext. We should come up with a good metricfor when is the best time to clean up
Painters and WebRender instancesfor defunct
RenderingContexts. This could perhaps be done via aWeakhandle to the
RenderingContext.Testing: This should not really change observable behavior, so should be
covered by existing tests.
Fixes: #13995
Closes: #40261