Reland "[PageColors] Integration of PageColors feature with NativeTheme"

This is a reland of commit da792e88b7ab6c96293af62d7ec62c7f6ecc51cf.
The issue was that we incorrectly assumed that
NativeTheme::ShouldUseDarkColors() would always return false initially.
However, on ChromeOS this function could sometimes return true.
To avoid this inconsistency, we explicitly set the desired value rather
than assuming anything about the native theme.

Original change's description:
> [PageColors] Integration of PageColors feature with NativeTheme
>
> This CL makes relevant state changes to the NativeTheme web instance
> when Page colors changes. This is done in the
> ColorSchemeNativeThemeObserver::OnNativeThemeUpdated method.
>
> In the ColorSchemeNativeThemeObserver::OnNativeThemeUpdated method,
> we preserves the current behavior if Page Colors is 'Off' and forced
> colors is false OR forced colors is true and Page Colors is
> 'High Contrast'. However, if that is not the case then:
>
> 1. Page Colors is 'Off' and forced colors is true, we override the
> state of forced colors for the native theme instance for web since the
> Page colors browser setting takes precedence over OS for web content.
> Here, we also watch for changes to the preferred color scheme and make
> sure we adjust the state appropriately.
> 2. Page Colors is one of the Contrast themes i.e. 'Dusk', 'Desert',
> 'Black', 'White'. Here, we set the forced colors state to true and
> other states appropriately for web content.
>
> This CL adds the color scheme observer as a native theme observer for
> Linux in order to receive the correct state changes from
> NativeThemeAura.
>
> Bug: 1231644
> Change-Id: I6792aadb9fead7a5d686c9cc0c67a29f986030ec
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4959835
> Reviewed-by: Peter Kasting <pkasting@chromium.org>
> Reviewed-by: Alison Maher <almaher@microsoft.com>
> Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
> Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
> Cr-Commit-Position: refs/heads/main@{#1230166}

Bug: 1231644
Change-Id: I516065d7a3b33e516257afa25e11fda24f8fccdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5074715
Reviewed-by: Alison Maher <almaher@microsoft.com>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1231446}
9 files changed
tree: 6659441fdf04f263ffc123713af1ae2632ac14ef
  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. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.