RPP: add warning banner when tracks are hidden.

This CL introduces a new banner which sits at the bottom of the timeline
to inform users that they have hidden tracks. When they do, they can
choose to show them all, enter track config mode, or dismiss the banner.

Once dismissed the banner will not return until they record/import
another trace.

This is a change to allow for a follow-up CL which will adjust the track
configuration persistence to be much more persistent; we will persist
config across traces. This means if you hide the "main thread" track on
one trace, it will be hidden in a future trace too. Because of this, we
want to introduce this banner to inform users when they have hidden
tracks.

Screenshot: screen/6vukmaa6cPQnKQ4

Bypass-Check-License: Only updates files, no new files are added.
Bug: 432663450
Change-Id: Ic4b5a8c6eadfa92a90a4f4744acaee23e07bd233
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6861972
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Alina Varkki <alinavarkki@chromium.org>
15 files changed
tree: 0a6bd30953edb07e6df490798274002680e65da3
  1. .gemini/
  2. .github/
  3. .vscode/
  4. build_overrides/
  5. config/
  6. docs/
  7. extension-api/
  8. extensions/
  9. front_end/
  10. inspector_overlay/
  11. node_modules/
  12. scripts/
  13. test/
  14. third_party/
  15. v8/
  16. .clang-format
  17. .clang-format-ignore
  18. .editorconfig
  19. .git-blame-ignore-revs
  20. .gitallowed
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .gn
  25. .mailmap
  26. .npmignore
  27. .npmrc
  28. .style.yapf
  29. .stylelintignore
  30. .stylelintrc.json
  31. AUTHORS
  32. BUILD.gn
  33. codereview.settings
  34. CONTRIBUTING.md
  35. DEPS
  36. DIR_METADATA
  37. eslint.config.mjs
  38. favicon.ico
  39. LICENSE
  40. OWNERS
  41. package-lock.json
  42. package.json
  43. PRESUBMIT.py
  44. README.md
  45. 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: