| commit | 50b0c0e46c8405292b411920fafd672a1c73cb51 | [log] [tgz] |
|---|---|---|
| author | Danil Somsikov <[email protected]> | Tue Dec 16 12:47:12 2025 |
| committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 16 20:06:14 2025 |
| tree | 4386cc492657a20cde53e64ac797ec9da4d04f14 | |
| parent | 5e129ae643894b4687f9cb8068b6e1ffb5cdeb3b [diff] |
Improve the a11y of the 3-dots menu and the rest of the LH report https://screencast.googleplex.com/cast/NjcyNjcxNjU5OTgyODQ4MHxiZDU0ZWM0Yy01OQ Bug: 40272029 Change-Id: I6f125b6b9e4a6f691e8028fd9bcd11fefd77aa5d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7261896 Reviewed-by: Connor Clark <[email protected]> Auto-Submit: Danil Somsikov <[email protected]> Commit-Queue: Danil Somsikov <[email protected]>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
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 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.
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/[email protected] 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.