New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 788722 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Canvas] use SurfaceLayer instead of TextureLayer for canvases

Project Member Reported by junov@chromium.org, Nov 27 2017

Issue description

We should stop using cc::TextureLayer in Canvas2DLayerBridge and DrawingBuffer, and use cc::SurfaceLayer instead.  This will help eliminate a lot of overhead caused by going through the renderer compositor at each animation frame.  It is now possible to synchronize viz::Surface with other surfaces in order to respect the atomicity of display updates that is required by the spec. Therefore, it should be possible to eliminate all uses cc::TextureLayer.
 

Comment 1 by junov@chromium.org, Nov 27 2017

Components: Blink>Canvas

Comment 2 by xing...@intel.com, Dec 7 2017

Cc: xing...@intel.com
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment