Alina Varkki
428dfcf039
Let's log the setting state every time that the first timeline is loaded in a new session. Logging on the first timeline load will make sure the navigation selection is only logged for people who use the performance panel. Logging on each first timeline load will allow us to get a number of people actually using either option instead of just the ones who try it out by toggling the setting. Bug: 313757601 Change-Id: If8a6a926e57c667f1e47eb3160cb17a3c547b2e6 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6099210 Auto-Submit: Alina Varkki <alinavarkki@chromium.org> Reviewed-by: Andres Olivares <andoli@chromium.org> Commit-Queue: Alina Varkki <alinavarkki@chromium.org>
Chrome DevTools frontend
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.
- DevTools user documentation: devtools.chrome.com
- Debugger protocol documentation: chromedevtools.github.io/devtools-protocol
- Awesome Chrome DevTools: github.com/paulirish/awesome-chrome-devtools
- Contributing to Chrome DevTools: goo.gle/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: goo.gle/devtools-contribution-guide-cdp
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
- @ChromeDevTools on Twitter
- Chrome DevTools mailing list: g/google-chrome-developer-tools
- File a new DevTools ticket: goo.gle/devtools-bug
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.