New first-run experience for console insights 1) Hover button and context menu entry appear even when DevTools setting is turned off 2) Opt-in teaser with link to settings 3) Once setting is turned on, insight is immediately generated 4) On subsequent runs, answer is generated immediately 5) In the case of enable setting, don't generate insight, new DevTools session -> show consent reminder once Screencasts: First-run experience: https://i.imgur.com/gBGlZVw.mp4 When first run happens in a new session: https://i.imgur.com/SQDaRSE.mp4 Doc (non-public): https://docs.google.com/document/d/1iGtygMGqqCUtZsq4SOcOKGGThgthdwzaTy24NCUmLMk Design (non-public): https://www.figma.com/design/aYuqExkCn0fbrltL9p85lq/Chrome-privacy-framework-for-Console-insights?node-id=1-63&node-type=CANVAS&m=dev Bug: b/350668580 Change-Id: I2ddf27e5d0bdf825f7d531246bd2a73123bffd92 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5830610 Commit-Queue: Wolfgang Beyer <[email protected]> Reviewed-by: Ergün Erdoğmuş <[email protected]>
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/[email protected] 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.
