commit | 4ca28454ce502d2a5ed6e13f775bd6c0a9f3a9a5 | [log] [tgz] |
---|---|---|
author | keno <kenoss@chromium.org> | Wed Jul 26 06:32:44 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 26 13:44:20 2023 |
tree | e9bdcd3bdf8be93b6dc9467e42154e06e0259464 | |
parent | 08ca9d229eb10645b3112346552fb874648ea4ff [diff] |
PreloadingDevTools: Prevent multiple duplicated warnings If a user is in a holdback group and opened DevTools for a page that contains multiple frames, warnings are stacked as many as the number of frames. This CL prevents this behavior. Bug: b/292180386 Change-Id: If118262cf382d2d468f0a5f3063f0573094287de Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4719448 Reviewed-by: Danil Somsikov <dsv@chromium.org> Commit-Queue: Ken Okada <kenoss@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