Gray out cycles to the start object in the Retainers pane In the Retainers pane, any object which is already opened at a higher level of the tree should be shown as gray and not provide the option to expand it further, to prevent the developer from accidentally traversing cycles. This functionality doesn't work, however, when the cycle is to the very first object which the user had originally selected. This CL sets the snapshot node ID on the root node of the Retainers pane so that findAncestorWithSameSnapshotNodeId can correctly determine when there is a cycle back to that starting node. Bug: 40805497 Change-Id: Ic9501944fa6d48855f055516839a6891d2a2c0e6 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5273876 Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
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 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