Fixed the Event Listener Leak in styles panel Every time the Styles panel rebuilt a CSS section, `StylePropertyTreeElement` would attach a new `LOCAL_VALUE_UPDATED` listener to the `SDK.CSSProperty`. Because these listeners were never removed, they accumulated. A single style update would eventually trigger thousands of `updateTitle()` calls, causing a CPU spike. Explicitly saving the bound listener to a private property (`#onPropertyLocalValueUpdated`) in `StylePropertyTreeElement` and leverage the `TreeElement` framework's native `onunbind()` lifecycle method to properly remove this listener when the element is detached. Bug: 487901682 Change-Id: I7bb7c3e338109497df072333294d10386324892d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7658087 Auto-Submit: Danil Somsikov <dsv@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Danil Somsikov <dsv@chromium.org>
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.