AI: Make DOM tree widget title configurable The DOM tree widget used in AI Assistance was hardcoded to display "LCP element" as its title. This is incorrect when the widget is used in other contexts, such as the Accessibility Agent. To fix this, we move the title and accessible reveal label configuration into the widget data itself. This allows each agent to provide contextually relevant titles (e.g., "LCP element" for performance, "Element" for accessibility) while keeping the rendering component generic. Fixed: 527391968 Change-Id: I099d010cda691f94a72f9d74d674fb3144c3cf55 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7993242 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Nicholas Roscino <nroscino@chromium.org> Reviewed-by: Piotr Paulski <piotrpaulski@chromium.org> Reviewed-by: Nicholas Roscino <nroscino@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
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/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.