Google Git
Sign in
chromium / chromium / src.git / 2b832346ea97bd660ef675f42813e9557feff344
commit2b832346ea97bd660ef675f42813e9557feff344[log] [tgz]
authorAdam Kassi Lahlou <adamkl@google.com>Tue Jun 17 12:19:00 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 17 12:19:00 2025
treef0eff9ae9550c662b109fdc0db958d7dd7bb2818
parent9b263dc9b3d1158cbd0788f1c6beab643c203185 [diff]
[Watermark 2.0] Apply user preferences : Opacity from Policy

This CL updates the watermark settings to fetch fill and
outline opacity values from the user's preference via PrefService.

Key changes include:
- Modify GetFillColor and GetOutlineColor to get preference values.
- Passing preference values after retrieving the user profile
from the browser in the browser view and
the data protection navigation code.
- Implementing precedence rules to get opacity from the desired source.

This approach provides more granular control over the watermark's
appearance.

Bug: 423935985
Change-Id: I2b44d0831c8dc3528faad50a5048804d6dc61eb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6637796
Reviewed-by: Jan Keitel <jkeitel@google.com>
Commit-Queue: Adam Kassi Lahlou <adamkl@google.com>
Reviewed-by: Nasser Al-shawwa <alshawwa@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1474890}
5 files changed
tree: f0eff9ae9550c662b109fdc0db958d7dd7bb2818
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. internal
  52. ios_internal
  53. native_client
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .cursorignore
  60. .git-blame-ignore-revs
  61. .gitallowed
  62. .gitattributes
  63. .gitignore
  64. .gitmodules
  65. .gn
  66. .mailmap
  67. .rustfmt.toml
  68. .vpython3
  69. .yapfignore
  70. ATL_OWNERS
  71. AUTHORS
  72. BUILD.gn
  73. CODE_OF_CONDUCT.md
  74. codereview.settings
  75. CPPLINT.cfg
  76. CRYPTO_OWNERS
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. SECURITY_OWNERS
  87. 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.