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>
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.