Implement color-scheme override per spec

For elements with color-scheme 'light', the color-scheme will be forced
to dark, and forced darkening will be performed on colors and images as
necessary.

For elements with color-scheme 'dark', no forced darkening will be
applied.

For elements with 'only light', the color-scheme will stay light, and no
force darkening will be applied. This behavior is behind a runtime flag.
With that runtime flag disabled, 'only light' will behave as 'light'.

There are two main changes that will affect the forced darkening in
WebView/WebLayer, and align it with the browser behavior:

1. The preferred color-scheme is now what is passed in via web
   preferences. We previously forced the preferred color-scheme to light
   in StyleEngine even for PREFER_MEDIA_QUERY_OVER_FORCE_DARK, which was
   a bug.

2. The color-scheme property will be forced to dark for all elements
   except those with 'only light'. That means we will render forms
   using dark UA styling instead of forcing light form controls to
   dark via GraphicsContext. Also, system colors will resolve to their
   dark version for forced darkening and not use the light versions and
   then invert them.

Bug: 1224806, 1228057

Change-Id: I0695f1bc1df6fd0de721e6bd73681dbbd479c77e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3137693
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Michael Bai <michaelbai@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#928615}
57 files changed
tree: dc09cdd8911855a33156081193bea057a0038780
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  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.