
The CSS image-rendering property determines the cc::FilterQuality to use when rendering an image. When blink renders an image, it stores the cc::FilterQuality in blink::ScopedImageRenderingSettings (this structure also includes DyanmicRangeLimit -- more on that later). When viz renders an image or a canvas, this property is set on the cc::TextureLayer. But not quite. We actually just set a boolean for "nearest neighbor". This property is already present on NinePatchLayer and TextureLayer, but will also be needed for VideoLayer and SurfaceLayer. Remove the various sub-class booleans and replace them with a member in the base class' cc::Layer::RareInputs. Plumb the DynamicRangeLimitMixture through the same path. Ensure that both of these properties cause a commit when changed (and add tests for this). Bug: 40277822 Change-Id: I4b702ce52e210e6ebd78e22d3425d8b728f5df6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6000365 Reviewed-by: ccameron chromium <ccameron@chromium.org> Reviewed-by: Fernando Serboncini <fserb@chromium.org> Commit-Queue: ccameron chromium <ccameron@chromium.org> Cr-Commit-Position: refs/heads/main@{#1387523}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.