Allow modifying headers in the Network Panel This CL allows the user to edit existing headers in the network panel's headers view. The edits will be added to the header overrides, such that upon refreshing the page, the response headers contain the edited values. Screencast: https://i.imgur.com/zlvzRyE.mp4 The edits are stored to disk and sent to the backend when the editable element loses focus. If there are multiple headers with the same name e.g. 'foo', these are treated as a single unit. This means that when overriding them, all 'foo' headers are removed and replaced with the override(s) for 'foo'. Bug: 1363132 Change-Id: Ib2ee738bfbe0974d12f0f854210afaa16f0a7259 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3879629 Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Wolfgang Beyer <wolfi@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project 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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools