commit | c1d059f5f56bbb65b77fd8aa697d1dde4d2e5be2 | [log] [tgz] |
---|---|---|
author | Natallia Harshunova <[email protected]> | Thu Jul 17 07:24:17 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 17 08:44:36 2025 |
tree | 886602012cbbbcc53c6bca37de2cda2100c7baf9 | |
parent | 2ec237cea2f63f07659729f2c84a004900b87fb6 [diff] |
Add VE logging to floating buttons This CL adds visual logging to the floating action buttons in the Elements, Network, and Sources panels. A `jslog-context` attribute was added to the `FloatingButton` component to allow specifying a logging context. This will allow tracking of clicks on these buttons for analytics. The visual logging debugging documentation was also updated to reflect the latest state of the debugging UI. Fixed: 429381292 Change-Id: I30a3227d99fbd26aa19962a2b56be21cb949ed10 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6728038 Reviewed-by: Danil Somsikov <[email protected]> Auto-Submit: Natallia Harshunova <[email protected]> Reviewed-by: Ergün Erdoğmuş <[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.