Fix hovered row colors for data grid in forced-colors mode This is a follow-up to https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3753276 The change was intended to remove striping behavior for data grid rows in high contrast mode to improve readability, and to indicate selected/ hovered rows with a highlight color. The above change added a ":not:hover" specifier to the CSS selector covering background color for odd-numbered data grid rows. Although hover colors were working in high contrast, the ":not:hover" addition meant that no rule was covering hovered elements in normal color mode, so odd rows would flash unstyled if hovered. Selected rows were also not quite working in high contrast. The "canvas" rule was taking precedence over the "highlight" rule for selected rows. This reverts the original change and adds the extra ":not(.dirty):not(.selected)" specifiers to the forced-color rules so that they will have the correct precedence w.r.t the to normal rules and each other. Data grid row colors now work as expected in both normal and high contrast color modes. There is no special hovering behavior in normal mode, and both hovered and selected rows are highlighted in high contrast mode. Bug: None Change-Id: If0206ca79f07f8542f1ff71bf52de00af9b48d98 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3965671 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Brandon Walderman <brwalder@microsoft.com>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools