commit | a2d015afbe57d7de380bc3a5c27047f83bbf03c8 | [log] [tgz] |
---|---|---|
author | Domenic Denicola <domenic@chromium.org> | Fri Jul 28 03:27:54 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 28 04:55:16 2023 |
tree | a91ba3983459d6ec704e1404ed123cdbae087154 | |
parent | 3c0cf09fbb3d976c36fa390ab5a348d7d8a09c08 [diff] |
PreloadingDevTools: update settings link Ever since issue 1385176 was fixed, all platforms have a sub-page of chrome://settings/cookies specifically for preloading. We can link directly to that. Bug: 1385176, 1410709 Change-Id: I35b38a91c17f10371cc1ef0b4886a3147dd6ca25 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4729061 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by: Danil Somsikov <dsv@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