|author||Simon Zünd <firstname.lastname@example.org>||Wed Feb 10 12:19:47 2021|
|committer||Commit Bot <email@example.com>||Thu Feb 11 05:58:54 2021|
Use developer.chrome.com link directly instead of shortener link We have a slight preference to remove url shortener links in DevTools as ownership of such links is not always clear. Drive-by: Include the link as a placeholder. This way the link is locked so it won't get translated, and it the link is also findable by "npm run check-external-links" verifier. Rfirstname.lastname@example.org, email@example.com Bug: chromium:965802 Change-Id: I12a9b3be53041932a13e74d996beb142e0388629 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2686660 Commit-Queue: Simon Zünd <firstname.lastname@example.org> Reviewed-by: Sigurd Schneider <email@example.com>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found in docs/triage_guidelines.md.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
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 open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: firstname.lastname@example.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools