commit | c5ad7dada701e6709ede62905edf83a7fae5be7e | [log] [tgz] |
---|---|---|
author | Danil Somsikov <dsv@chromium.org> | Fri Mar 03 16:39:19 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 06 14:02:34 2023 |
tree | b1dee29d9d2122c74634c84dcae7eda00ca10c83 | |
parent | 772ce6cf141104a77b595fa69bfab83c144068b8 [diff] |
Use scoped TargetManager API in the PropertiesWidget Bug: 1417112 Change-Id: I6d766c0682d9ed920fa2a5b2cfbbd872fe81e4dd Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4307580 Auto-Submit: Danil Somsikov <dsv@chromium.org> Reviewed-by: Wolfgang Beyer <wolfi@chromium.org> Commit-Queue: 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