Joshua Thomas
08b058fcbc
Issues fixed by this CL: 1. Padding was removed from below the table and left border was removed from data grid so that were was not a double border with the sidebar divider 2. Filter chips are only shown when there is an associated entry in the table. E.g. "Blocked" will not be shown if all entries were "Allowed" 3. String updates. Before: https://screenshot.googleplex.com/ASnzNBP9h5fyr9n.png After: https://screenshot.googleplex.com/5Ddn4cydTdKad8o.png Bug: b/365737493,b/382254647,b/382259750,b/382260846 Change-Id: I54cc3a8d488a40026e0a3f6d497e0b782c407c20 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6141933 Reviewed-by: Shuran Huang <shuuran@chromium.org> Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Joshua Thomas <masnoble@chromium.org>
Chrome DevTools frontend
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
Source code and documentation
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
- DevTools user documentation: devtools.chrome.com
- Debugger protocol documentation: chromedevtools.github.io/devtools-protocol
- Awesome Chrome DevTools: github.com/paulirish/awesome-chrome-devtools
- Contributing to Chrome DevTools: goo.gle/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: goo.gle/devtools-contribution-guide-cdp
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
- @ChromeDevTools on Twitter
- Chrome DevTools mailing list: g/google-chrome-developer-tools
- File a new DevTools ticket: goo.gle/devtools-bug
There are a few options to keep an eye on the latest and greatest of DevTools development:
-
Follow What's new in DevTools.
-
Follow Umar's Dev Tips.
-
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
-
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
-
Checkout all open DevTools tickets on crbug.com
-
Use Chrome Canary and poke around the experiments.