commit | 060d382e7abdcff8d353b8422e618cb35c1c4a07 | [log] [tgz] |
---|---|---|
author | Christopher Cameron <ccameron@chromium.org> | Wed Oct 04 23:12:42 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 04 23:12:42 2023 |
tree | f2612b8af2634357f5c71d05e00549c2bd537318 | |
parent | 12d607016c31ea13579e897740c765be189ed6eb [diff] |
HDR images: Propagate headroom to gpu::raster::RasterDecoderImpl HDR images have their tonemapping "baked in" during image decode. This means that if the HDR headroom changes (which it does), we have to re-decode the image. This also significantly complicates the implementation of the dynamic-range-limit CSS property. Fix this situation by having the tonemapping be applied at raster time, on the service side. In order to perform tonemapping, the RasterDecoder needs to know the HDR headroom. Plumb that information through the following path: - cc::TileManager::CreateRasterTask - already has the parameter) - cc::RasterSource::PlaybackSettings - add new member) - gpu::raster::RasterInterface::BeginRasterCHROMIUM - (command buffer glue) - gpu::raster::RasterDecoderImpl::DoBeginRasterCHROMIUM In the next patch, this will be used to apply tonemapping on the service side. Add tests for the client side of the propagation. End-to-end testing will require the tonemapping change (which will be in the next patch). Bug: 1483235 Change-Id: I3a687083859d1d9ccbec6ef12956705ea89da935 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4909841 Reviewed-by: Khushal Sagar <khushalsagar@chromium.org> Commit-Queue: ccameron chromium <ccameron@chromium.org> Cr-Commit-Position: refs/heads/main@{#1205543}
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.