[network] Show memory inspector in the "Response" tab for binary content This CL changes the Network > Response tab to show the linear memory inspector for network requests with a binary payload instead of nothing. Until recently we would blindly decode binary content in some cases (but not all). This only made sense if the binary content actually had some valid ascii sequences in it's content as the rest would be garbage. This CL restores the ability to inspect binary content, but via the linear memory inspector which produces a hexdump of the content. This allows developers to still check ascii sequences in binary content and even check the binary data directly. R=kimanh@chromium.org Fixed: 372158884 Change-Id: Ifdac1607b767a1522343e9e9bfc161a0e5d2ffc3 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5917828 Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Commit-Queue: Simon Zünd <szuend@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.