commit | 89d0607c37299b03eb01439562767ef613e99ae0 | [log] [tgz] |
---|---|---|
author | Alison Maher <almaher@microsoft.com> | Fri Jan 22 18:58:05 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 22 18:58:05 2021 |
tree | 8878767295626d52b63749e0a18435d5f555e2f9 | |
parent | f3e964c0ecc9c5da85a6d37419cb03a3aef13aa0 [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}
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.