Adam Raine
f2ba87197e
This reverts commit 6333612700.
Reason for revert: Obsolete with https://crrev.com/6404821
Original change's description:
> [NetworkRequestDetails] Fix initiator row styling
>
> The initiator row was separated because the link can be very long. This
> CL groups the initiator with everything else but applies `ellipis` to
> contain the size.
>
> Bug: 406864076
> Change-Id: I7088b64f7b3154e457a46f515b35908102c7cd5e
> Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6404927
> Auto-Submit: Adam Raine <asraine@chromium.org>
> Commit-Queue: Adam Raine <asraine@chromium.org>
> Reviewed-by: Paul Irish <paulirish@chromium.org>
Bug: 406864076
Change-Id: I9fa423e170455f4235bb5feb7c77a35691f6b3a7
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6410873
Commit-Queue: Adam Raine <asraine@chromium.org>
Reviewed-by: Paul Irish <paulirish@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
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.