ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: oxide
     Importance: Medium
         Status: Triaged

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
       Status: New => Triaged

** Description changed:

  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.
+ passing the renderer compositor's Surface directly to it. There's
+ probably a performance benefit from doing this.

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1630200

Title:
  Investigate not using a LayerTreeHost on the browser side

Status in Oxide:
  Triaged

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1630200/+subscriptions