commit | 08985dafaca72e571068309ad0dd8266574d4edf | [log] [tgz] |
---|---|---|
author | W. James MacLean <wjmaclean@chromium.org> | Tue Oct 22 14:54:20 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 22 14:54:20 2024 |
tree | 8ff9f927de9e913be655928467c02aca8ce1529d | |
parent | 856d1de899fb5e13096e6ae56b0a781480aeb59f [diff] |
Tweak SurfaceLayerImpl DrawQuad transform for pixel-alignment. This CL adds code (behind a disabled-by-default feature) to snap DrawQuads for SurfaceLayerImpl to the pixel grid. This is necessary to reduce/remove fuzziness in text in out-of-process iframes (OOPIFs) when a fractional scale-transform is applied to the OOPIF's owner. Since this tweak can also affect other users of SurfaceLayerImpl (e.g. <canvas>), initially this will land disabled. This CL also adds tests for scaled OOPIFs vs. same-process iframes (with different scrollbar configurations), and OOPIFs with a fractional translate-transform. Since the new OOPIF behavior differs from same-process iframes rendering the same content, and since the OOPIF behavior appears to be an improvement, the tests use fuzzy pixel matching to allow these tests to use the same-process results as reftest expectations. The test are expected to fail when the feature is not enabled. Bug: 359279545 Change-Id: Ic8e13a68462f98d39e72a29c809541533933df62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5842653 Commit-Queue: James Maclean <wjmaclean@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/main@{#1372031}
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.