Shared Storage: Remove Shared Storage support from DevTools

Chrome has announced that the current approach to third-party cookies
will be maintained, and adoption of the Shared Storage API has since
decreased significantly. Consequently, Shared Storage is being
deprecated and removed from Chrome as part of the Privacy Sandbox
deprecation plan. Previously, DevTools supported Shared Storage event
tracking and data introspection in the Application panel, along with
worklet target debugging in the SDK. Leaving these components in place
would result in obsolete UI elements and dead code once the web
platform API is removed.

This commit removes Shared Storage support from DevTools:
- Deletes the Shared Storage views, components, model, and tree
  elements from the Application panel (SharedStorageEventsView,
  SharedStorageItemsView, SharedStorageMetadataView, etc.).
- Removes SHARED_STORAGE_WORKLET target handling, event breakpoints,
  and instrumentation from the core SDK (Target, ChildTargetManager,
  EventBreakpointsModel, CategorizedBreakpoint, and
  ExecutionContextSelector).
- Removes associated unit tests, end-to-end tests, and build target
  references.

Removing these surfaces aligns DevTools with the web platform removal
schedule, maintains code health, and prevents developer confusion from
non-functional storage introspection tools.

Bug: 535990398,462465887
Change-Id: Ia0c5d8197e102cad86105f116a0542ff52b4b0b4
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8155881
Reviewed-by: Connor Clark <cjamcl@chromium.org>
Reviewed-by: Danil Somsikov <dsv@chromium.org>
Commit-Queue: Cammie Smith Barnes <cammie@chromium.org>
38 files changed
tree: 1e22abb1be728d59a1ebbc59d8c697ea8ed67970
  1. .agents/
  2. .gemini/
  3. .github/
  4. .vscode/
  5. build_overrides/
  6. config/
  7. docs/
  8. extension-api/
  9. extensions/
  10. front_end/
  11. inspector_overlay/
  12. mcp/
  13. node_modules/
  14. scripts/
  15. test/
  16. third_party/
  17. v8/
  18. .clang-format
  19. .clang-format-ignore
  20. .editorconfig
  21. .env.template
  22. .geminiignore
  23. .git-blame-ignore-revs
  24. .gitallowed
  25. .gitattributes
  26. .gitignore
  27. .gitmodules
  28. .gn
  29. .mailmap
  30. .npmignore
  31. .npmrc
  32. .style.yapf
  33. .stylelintignore
  34. .stylelintrc.json
  35. AUTHORS
  36. BUILD.gn
  37. codereview.settings
  38. CONTRIBUTING.md
  39. DEPS
  40. DIR_METADATA
  41. eslint.config.mjs
  42. favicon.ico
  43. LICENSE
  44. OWNERS
  45. package-lock.json
  46. package.json
  47. PRESUBMIT.py
  48. README.md
  49. SECURITY.md
  50. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

Source code and documentation

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.

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

There are a few options to keep an eye on the latest and greatest of DevTools development: