Fix difference in Fluent scrollbar grays caused by their alpha

Fluent scrollbars grays are currently achieved by applying a certain
transparency to a pure white (255, 255, 255) or black (0,0,0) color.
This CL changes the way to achieve the desired color from applying an
alpha to a white or black, to directly setting the color of the gray
that we want with an alpha of 1.
The reason for this change is that the transparencies cause light mode
scrollbar gray parts (non-hovered) to be painted with different shades
of gray. Main threaded thumbs are being drawn at a shade of gray darker
than composited scrollbars' thumbs, and win10 arrows are also being
drawn with a darker gray.
This doesn't happen in dark mode, nor with the hovered/pressed colors,
but these colors are receiving the same treatment in order to avoid
potential future problems.
The new colors were chosen by picking the final rendered color of
the scrollbar parts. For example, light themed non-hovered gray is a
gray with the RGB values (139,139,139).

The root cause of this issue is suspected to be caused by a different
rounding mechanism used to apply the alpha in the different call ops.
For example, for win10 vs win11 arrows, the color is the same but the
skia paint function called is different (see
NativeThemeFluent::PaintArrow).

Most rebaselines are due to a few anti aliasing pixels containing
different values, except for win10 arrows and main threaded thumbs
which are completely replaced by the new selected color.

Bug: 1517769
Change-Id: Ic258a0e3a26a8bee96c005df6c721a4f6ab1f582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5191003
Reviewed-by: Yaroslav Shalivskyy <yshalivskyy@microsoft.com>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Commit-Queue: Gaston Rodriguez <gastonr@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1253636}
44 files changed
tree: 8a06a707573e0d3002fc18a438f4c6934dd61946
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. WATCHLISTS
README.md

Logo 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.