AI Assistance: Deduplicate DOM storage partitions across subtargets When a page contains same-origin iframes or subtargets, each target creates its own DOMStorageModel instance containing identical storage keys. As resolveDOMStorages iterated across all models in the primary page tree, it returned duplicate DOMStorage instances for each subtarget sharing that partition. Track seen storage keys within resolveDOMStorages to yield each unique storage partition only once across all models in the target tree. Fixed: 545947116 Change-Id: Ib3e8c9edcbadd952e4063b92fde2ce458b52ac33 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8301276 Reviewed-by: Alina Varkki <alinavarkki@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Alina Varkki <alinavarkki@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.