Google Git
Sign in
chromium / chromium / src / 89d0607c37299b03eb01439562767ef613e99ae0
commit89d0607c37299b03eb01439562767ef613e99ae0[log] [tgz]
authorAlison Maher <almaher@microsoft.com>Fri Jan 22 18:58:05 2021
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jan 22 18:58:05 2021
tree8878767295626d52b63749e0a18435d5f555e2f9
parentf3e964c0ecc9c5da85a6d37419cb03a3aef13aa0 [diff]
Force caret-color in Forced Colors Mode

When Forced Colors happened at computed value time, caret-color would
pick up the forced color through currentcolor. However, now that
we are forcing colors at used value time, it appeared that caret-color
regressed since it no longer picks up the forced currentcolor.

This change adds caret-color to the properties that are adjusted in
Forced Colors Mode, and forces it to use the forced currentcolor.

I've opened a new spec issue to address this, as well as a few other
color properties that I noticed would also be affected by this:
https://github.com/w3c/csswg-drafts/issues/5873

(cherry picked from commit 80f9a6eaee3e08e1e0e1eb58302d7bf6a54c28b0)

Bug: 1166392
Change-Id: I239700441ed17bfd0b33443887a0c72793843cf1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627779
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Original-Commit-Position: refs/heads/master@{#845398}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644149
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/branch-heads/4389@{#146}
Cr-Branched-From: 9251c5db2b6d5a59fe4eac7aafa5fed37c139bb7-refs/heads/master@{#843830}
11 files changed
tree: 8878767295626d52b63749e0a18435d5f555e2f9
  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. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.