Dan Clark
bfe1683fe8
The CSS highlight inheritance model specified at [1] introduces a parallel cascade for highlight pseudos (::selection, ::spelling-error, ::grammar-error, and ::highlight). This change updates the style pane to include this parallel pseudo cascade when displaying rules for highlight pseudos. The corresponding backend change is at [2]. A screenshot of what this looks like can be viewed at [3]. [1] https://drafts.csswg.org/css-pseudo-4/#highlight-cascade [2] https://chromium-review.googlesource.com/c/chromium/src/+/3461424 [3] https://docs.google.com/document/d/10qOm--onzEQe6HT6z1kUqzAVOLkN7Rc42wnrahRdsr0/edit?usp=sharing Bug: 1024156 Change-Id: I1c8a034d5d956acc6238a0965fd8dfdb92f2399b Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3502175 Reviewed-by: Johan Bay <jobay@chromium.org> Reviewed-by: Delan Azabani <dazabani@igalia.com> Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Dan Clark <daniec@microsoft.com>
Chrome DevTools frontend
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
Source code
The frontend is available on chromium.googlesource.com.
Design guidelines
Please be aware that DevTools follows additional development guidelines.
Issue triage
The issue triage guidelines can be found in docs/triage_guidelines.md.
Workflows
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
Additional references
- DevTools documentation: devtools.chrome.com
- Debugging protocol docs and Chrome Debugging Protocol Viewer
- awesome-chrome-devtools: recommended tools and resources
- Contributing to DevTools: bit.ly/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: docs.google.com
- DevTools Design Review Guidelines: design_guidelines.md
Source mirrors
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.
Getting in touch
-
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