Investigate not using a LayerTreeHost on the browser side

Bug #1630200 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Triaged
Medium
Unassigned

Bug Description

The webview compositor uses a full LayerTreeHost, but we effectively only have a single layer (and that's a SurfaceLayer). We should be able to do away with the LayerTreeHost entirely, using only a cc::Display and passing the renderer compositor's Surface directly to it. There's probably a performance benefit from doing this.

Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.