Jack Franklin
78d3973605
This is a reland of commit 9995b96203
Original change's description:
> RPP: create new annotations AI agent
>
> Required mostly for metrics so we can track its usage accurately rather
> than bundled in with the existing "Ask AI" integration.
>
> (Googlers: see the attached bug for a link to the backend CL, this needs
> to land first before this can land).
>
> Bug: 406795908
> Change-Id: Ibf0fff042f72a6e622e9d9d9e87769a71feb23af
> Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6407494
> Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org>
> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Bug: 406795908
Change-Id: I0c3bc41014a1f1f120fbb4f68f701eafcb4216a0
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6405318
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Nikolay Vitkov <nvitkov@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.