Currently ImageSkia is used as a rasterized image source in the code base. This assumption is used throughout the code base leading to early rasterization of the images on the UI thread. This also means the UI needs to be aware of the current device scale which is cc's job.
ImageSkia should support drawables, which can delay the rasterization of vector images & icons to the cc worker threads (or even the GPU with OOPR). This will also hand over cc the control for scaling the images and offload rasterization task away from the UI thread. It will also allow any image source backed by a drawable to be added with ease (Skottie, SVG, current .icon format, any other vector image source).
Comment 1 by malaykeshav@chromium.org
, Sep 19