Modify UIResourceLayer to be shareable between different UI compositors |
||||||||
Issue descriptionTo permit Chrome for Mus (and Linux etc.) to more efficiently make use of the DisplayCompositor, modify UIResourceLayer to be shareable between all UI compositors in the Chrome browser
,
Dec 9 2016
,
Dec 9 2016
Chrome doesn't use ui::ResourceLayer at all yet. We should explicitly use it.
,
Dec 9 2016
,
Jul 18 2017
What's the current state of this task?
,
Jul 18 2017
We have investigated where (and how) we could use cc::UIResourceLayer in UI [1]. We haven't found an owner yet. [1] https://docs.google.com/document/d/1u9RZTyxdXP6zJ9skfanLPRowtvmciko95fZO1ZTZLiY/edit#heading=h.38c6t6ta13yq
,
Nov 21 2017
,
Aug 15
Sadrul, correct me if I'm wrong, but I don't believe this is mash specific.
,
Aug 16
It's a performance win for the UI and may be necessary for oopash. Saman: this overlaps with the GPU raster work so over to you to organize.
,
Aug 20
I'm tagging with multi-process mash for now.
,
Aug 20
This would be an optimization for all platforms that use ui::Compositors, so this affects Windows etc. too (when there are multiple browser windows). As stated earlier in the bug though, we don't use UIResourceLayer for UI at all at the moment. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rjkroege@chromium.org
, Dec 8 2016