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>
8 files changed
tree: 6e34758d334feb9b49955bbaf24fb571249dba89
  1. .agents/
  2. .gemini/
  3. .github/
  4. .vscode/
  5. build_overrides/
  6. config/
  7. docs/
  8. extension-api/
  9. extensions/
  10. front_end/
  11. inspector_overlay/
  12. mcp/
  13. node_modules/
  14. scripts/
  15. test/
  16. third_party/
  17. v8/
  18. .clang-format
  19. .clang-format-ignore
  20. .editorconfig
  21. .env.template
  22. .geminiignore
  23. .git-blame-ignore-revs
  24. .gitallowed
  25. .gitattributes
  26. .gitignore
  27. .gitmodules
  28. .gn
  29. .mailmap
  30. .npmignore
  31. .npmrc
  32. .style.yapf
  33. .stylelintignore
  34. .stylelintrc.json
  35. AUTHORS
  36. BUILD.gn
  37. codereview.settings
  38. CONTRIBUTING.md
  39. DEPS
  40. DIR_METADATA
  41. eslint.config.mjs
  42. favicon.ico
  43. LICENSE
  44. OWNERS
  45. package-lock.json
  46. package.json
  47. PRESUBMIT.py
  48. README.md
  49. SECURITY.md
  50. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

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.

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

There are a few options to keep an eye on the latest and greatest of DevTools development: