"Back/forward cache" is the official name of BFCache. https://groups.google.com/a/google.com/g/chrome-bfcache/c/WmRKH29afrw/m/JiXi0p0sBAAJ?utm_medium=email&utm_source=footer This CL spells lowercase b when not starting a sentence. This CL normalizes all notations. Deactivate tests in Chromium: I356efe231e9f7547573eb94e2244b9e5e19266cf Activate tests in Chromium: Ia69f55a42a9ce977ef89e5ec1f3398e874a88765 Bug: 1271044 Change-Id: Iadd4e198143572188a5a66b28834cf7237738482 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3281075 Commit-Queue: Riho Isawa <rhisawa@google.com> Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Yuzu Saijo <yuzus@chromium.org> Reviewed-by: Darren W <djw@chromium.org> Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
Chrome DevTools frontend
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
Source code
The frontend is available on chromium.googlesource.com.
Design guidelines
Please be aware that DevTools follows additional development guidelines.
Issue triage
The issue triage guidelines can be found in docs/triage_guidelines.md.
Workflows
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
Additional references
- DevTools documentation: devtools.chrome.com
- Debugging protocol docs and Chrome Debugging Protocol Viewer
- awesome-chrome-devtools: recommended tools and resources
- Contributing to DevTools: bit.ly/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: docs.google.com
- DevTools Design Review Guidelines: design_guidelines.md
Source mirrors
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.
Getting in touch
-
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