Merge surface_manager & surface_factory functionality in "display_compositor" feature
Reported by
kavitha....@gmail.com,
Jan 24 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Feature imrpvomentand code-merge suggested 2. 3. What is the expected behavior? The proposal is to merge the surface_manager & surface_factory functions to simplify * cleanup some of the book-keeping associated with surfaces corresponding to CompositorFrameSink What went wrong? This is a proposal to simplify the code around CompositorFrameSinks & Surfaces in cc/surfaces, cc/trees & cc/output. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0
,
Jan 24 2017
,
Jan 25 2017
,
Jan 26 2017
,
May 3 2017
We are currently merging SurfaceFactory into CompositorFrameSinkSupport but we have no plans to merge that into SurfaceManager so I'm marking as WONTFIX.
,
Jun 13 2017
,
Feb 26 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by a.suchit@chromium.org
, Jan 24 2017Labels: -OS-Windows -Pri-2 -Via-Wizard-Other displaycompositor OS-All Pri-3