commit | 0e0de1db43cf94840bec724f14a21674d455b8ca | [log] [tgz] |
---|---|---|
author | Guangyue Xu <guangyue.xu@microsoft.com> | Tue Jul 08 23:58:28 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 09 18:31:05 2025 |
tree | ffeab64e2bc4f57b857b7ef8bd9fa0689c57dd7b | |
parent | a53fa821284d7ebea743f1322357dc3abadc7921 [diff] |
Show number of CSS invalidation in DevTools performance panel In the Selector stats table, a new column is added to display the number of invalidated nodes for each selector. With the information, developers can identify the CSS rules that invalidate a large number of nodes to reduce over-invalidation, so that they can improve long Recalculate style events by rewriting expensive selectors. More details can be found in this design doc: https://docs.google.com/document/d/1K7ng5TdeyJemKqXP2I7r1IQPYz4Xb059E6d7M2B8SxY/edit?tab=t.0 Bug: 379886422 Change-Id: I57daf28191cd002624f1fbbfd843c6b009316eaf Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6333633 Reviewed-by: Paul Irish <paulirish@chromium.org> Commit-Queue: Guangyue Xu <guangyue.xu@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 Chromium DevTools 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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.