mirror of
https://github.com/servo/servo.git
synced 2025-08-06 14:10:11 +01:00
Auto merge of #26823 - jdm:single-renderapi, r=asajeffrey
Update webrender These changes reflect changes in webrender's API that make RenderApiSender and RenderApi objects more challenging to share. This PR moves us to a model where: * the compositor owns the main RenderApi object * other threads that need to create transactions or manipulate fonts proxy those operations to the compositor (script/layout use IPC, while other threads use non-IPC channels) * the webgl thread owns its own independent RenderApi
This commit is contained in:
commit
7eacfa4f0d
51 changed files with 421 additions and 331 deletions
|
@ -234,6 +234,12 @@ impl StackingContext {
|
|||
));
|
||||
}
|
||||
|
||||
// TODO(jdm): WebRender now requires us to create stacking context items
|
||||
// with the IS_BLEND_CONTAINER flag enabled if any children
|
||||
// of the stacking context have a blend mode applied.
|
||||
// This will require additional tracking during layout
|
||||
// before we start collecting stacking contexts so that
|
||||
// information will be available when we reach this point.
|
||||
builder.wr.push_stacking_context(
|
||||
LayoutPoint::zero(), // origin
|
||||
self.spatial_id,
|
||||
|
@ -245,8 +251,7 @@ impl StackingContext {
|
|||
&vec![], // filter_datas
|
||||
&vec![], // filter_primitives
|
||||
wr::RasterSpace::Screen,
|
||||
false, // cache_tiles,
|
||||
false, // false
|
||||
wr::StackingContextFlags::empty(),
|
||||
);
|
||||
|
||||
true
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue