chrome-devtools-frontend 1.0.1581449 → 1.0.1582745

package/agents/prompts/merging-devtools-module.md

@@ -0,0 +1,144 @@
+# Workflow: Merging a DevTools Submodule into its Parent
+
+This document outlines the process for merging a submodule (e.g., `panels/timeline/extensions`) into its parent module (e.g., `panels/timeline`) within the DevTools build system. The goal is to simplify the build configuration by consolidating `BUILD.gn` files while keeping the original source file directory structure.
+
+## Prerequisites
+
+You will need the following information:
+-   **Parent Module Path:** The path to the directory containing the primary module.
+-   **Child Module Path:** The path to the directory of the submodule to be merged.
+
+## Workflow Steps
+
+### 1. Analyze Build Configurations
+
+Read the contents of the `BUILD.gn` file from both the child module and the parent module. Identify the following from the child's `BUILD.gn`:
+-   The list of `sources` in the `devtools_module`.
+-   The list of `deps` (dependencies) in the `devtools_module`.
+-   The `entrypoint` for the `devtools_entrypoint("bundle")`.
+
+### 2. Modify the Parent `BUILD.gn`
+
+Edit the `BUILD.gn` file in the parent module's directory to incorporate the child module's configuration.
+
+1.  **Add Child's Sources:** Append the list of `sources` from the child's `devtools_module` to the parent's `sources` list. Remember to maintain the relative path from the parent's directory (e.g., `extensions/ExtensionUI.ts`).
+2.  **Merge Dependencies:** Add the `deps` from the child's `devtools_module` to the parent's `deps` list. Remove any duplicate entries.
+3.  **Remove Child Bundle Dependency:** Delete the dependency on the child's bundle from the parent's `deps` list (e.g., remove `./extensions:bundle`).
+
+### 3. Delete the Child `BUILD.gn`
+
+Once the parent `BUILD.gn` is updated and contains all the necessary information, the child's `BUILD.gn` is no longer needed. Delete it.
+
+```bash
+rm <child_module_path>/BUILD.gn
+```
+
+### 4. Update `devtools_grd_files.gni`
+
+The global `.gni` file that lists all resources needs to be updated to reflect that the child module is no longer a separate, bundled entrypoint.
+
+1.  **Locate and Read the File:** Open `config/gni/devtools_grd_files.gni`.
+2.  **Remove Bundled Source:** Find and remove the line for the child's bundled JavaScript file from the `grd_files_bundled_sources` list. This path usually corresponds to the child's `entrypoint`.
+3.  **Add Unbundled Sources:** Add the paths to all of the child's original TypeScript source files (`.ts`) to the `grd_files_unbundled_sources` list.
+
+---
+
+## Example: Merging `panels/timeline/extensions` into `panels/timeline`
+
+-   **Parent Module:** `panels/timeline`
+-   **Child Module:** `panels/timeline/extensions`
+
+### 1. `panels/timeline/BUILD.gn` Modification
+
+**Before:**
+```gni
+devtools_module("timeline") {
+  sources = [
+    ...
+    "UIDevtoolsUtils.ts",
+  ]
+
+  deps = [
+    ...
+    "./components:bundle",
+    "./extensions:bundle",
+    "./overlays:bundle",
+    ...
+  ]
+}
+```
+
+**After:**
+```gni
+devtools_module("timeline") {
+  sources = [
+    ...
+    "UIDevtoolsUtils.ts",
+    "extensions/ExtensionUI.ts", # Added from child
+  ]
+
+  deps = [
+    ...
+    "./components:bundle",
+    # "./extensions:bundle", # Removed
+    "./overlays:bundle",
+    ...
+    # Dependencies from extensions/BUILD.gn are merged here
+    "../../../ui/components/helpers:bundle",
+    "../../../ui/components/render_coordinator:bundle",
+    "../../../ui/legacy:bundle",
+  ]
+}
+```
+
+### 2. `panels/timeline/extensions/BUILD.gn` Deletion
+
+```bash
+rm front_end/panels/timeline/extensions/BUILD.gn
+```
+
+### 3. `config/gni/devtools_grd_files.gni` Modification
+
+**Before:**
+```gni
+grd_files_bundled_sources = [
+  ...
+  "front_end/panels/timeline/components/components.js",
+  "front_end/panels/timeline/extensions/extensions.js",
+  "front_end/panels/timeline/overlays/overlays.js",
+  ...
+]
+
+grd_files_unbundled_sources = [
+  ...
+  "front_end/panels/timeline/extensions/ExtensionUI.ts", # This might not have been present before
+  ...
+]
+```
+
+**After:**
+```gni
+grd_files_bundled_sources = [
+  ...
+  "front_end/panels/timeline/components/components.js",
+  # "front_end/panels/timeline/extensions/extensions.js", # Removed
+  "front_end/panels/timeline/overlays/overlays.js",
+  ...
+]
+
+grd_files_unbundled_sources = [
+  ...
+  "front_end/panels/timeline/extensions/extensions.ts", # Added
+  "front_end/panels/timeline/extensions/ExtensionUI.ts",   # Added
+  ...
+]
+```
+
+## Removing Barrel Files
+
+After merging modules, you may still have remaining barrel files (e.g. `index.ts` or `extensions.ts` that just re-export other files). These should be removed to simplify the module structure.
+
+Manually updating all imports that rely on these barrels can be tedious and error-prone. The tool [unbarrelify](https://github.com/webpro/unbarrelify) can automate this process. It analyzes your codebase and replaces imports from barrel files with direct imports from the source files.
+
+**Usage:**
+Follow the instructions in the [unbarrelify repository](https://github.com/webpro/unbarrelify) to install and run the tool on your project. This is highly recommended to complete the refactoring process efficiently.

package/agents/prompts/ui-widgets.md

@@ -0,0 +1,351 @@
+## UI Widget Framework Guide (MVP Architecture)
+
+Adhere strictly to the Model-View-Presenter (MVP) architecture.
+
+* **Models** (`front_end/models/`): Handle business logic and application state. MUST NOT have knowledge of the UI.
+* **Presenters (`Widget`)**: Orchestrate data flow, manage UI-specific state, and handle interactions.
+* **Views (`function`)**: Purely presentational. Stateless functions that receive data/callbacks and render using `lit-html`.
+
+**Refactoring Note:** When refactoring legacy widgets to this framework, the widget's class name MUST NOT be changed. If you're refactoring a UI piece that uses shadow root (e.g. custom HTMLElements) to a Widget, make sure to update its styles to wrap the rules with a `@scope to (devtools-widget > *)` rule.
+
+### Presenter (`Widget`) Rules
+
+* Location: Co-located in the same file as its View.
+* MUST extend a base `UI.Widget` class (e.g., `UI.Widget.Widget`). Note that `UI.Widget.Widget` is not an `HTMLElement` and must be appended via `.show()` or `<devtools-widget>`.
+* Constructor MUST assign the injected view function to a private `#view` field.
+* Constructor MUST call `super()`. If taking `element?: HTMLElement`, pass it to `super(element)`. `super(true)` is forbidden.
+* Styling MUST be handled within the View. `this.registerCSSFiles()` is forbidden.
+* Initial render MUST be triggered in `override wasShown(): void` by calling `this.requestUpdate()`.
+* MUST hold all UI state as private class fields (e.g., `#counter`).
+* To schedule a UI update, MUST call `this.requestUpdate()`. `performUpdate()` MUST NOT be called directly.
+
+### View (`function`) Rules
+
+* MUST be a pure function, typically named `DEFAULT_VIEW`, in the same file as the Presenter.
+* MUST use the signature: `(input: ViewInput, output: ViewOutput, target: HTMLElement)`.
+  * `input`: Data and event handlers from the Presenter.
+  * `output`: Callbacks for imperative actions (e.g., focus) provided to the Presenter. If unused, the `output` parameter should be typed as `undefined` in the view's signature, and `undefined` should be passed from the presenter.
+  * `target`: The HTML element to render into.
+* The `input` parameter MUST NOT be destructured. Always use `input.propertyName`.
+* Responsibility: Render a `lit-html` template into `target`.
+* MUST NOT hold state, fetch data, or perform business logic.
+
+#### Helper Functions in Views
+
+Complex views can be broken down using helper functions defined inside `DEFAULT_VIEW` to access `input` and `output`.
+
+```ts
+// clang-format off
+const DEFAULT_VIEW = (input: ViewInput, output: ViewOutput, target: HTMLElement): void => {
+  const renderHeader = (): Lit.LitTemplate => {
+    return html`<h1>${input.title}</h1>`;
+  };
+  // ...
+  render(html`
+    <div class="child-widget">
+      ${renderHeader()}
+    </div>
+  `, target);
+};
+// clang-format on
+```
+
+### Composition (`<devtools-widget>`)
+
+* To render a child widget, the parent's View MUST use `<devtools-widget>`.
+* Configuration is passed via the `.widgetConfig` property using `UI.Widget.widgetConfig()`.
+* Properties passed from a parent MUST be declared as public fields on the child presenter class.
+* The framework automatically updates these properties and calls `requestUpdate()` on the child when the parent re-renders.
+
+## Refactoring Legacy Components
+
+When migrating imperative components (extending `UI.VBox`, `UI.Panel`, or `HTMLElement`) to the MVP architecture:
+
+1.  **Analyze Rendering Logic:** Identify where DOM is created (constructor, `wasShown`, imperative methods). This logic moves to the `DEFAULT_VIEW`.
+2.  **Convert Base Class:**
+    *   Prefer extending `UI.Widget.Widget`.
+    *   **Special Case:** If the component *must* extend `UI.Panel.Panel` or `UI.Dialog.Dialog` (to retain specific functionality), you cannot use `requestUpdate()`. Instead, call `this.performUpdate()` directly on state changes.
+3.  **State Migration:** Move DOM-stored state to private class fields.
+4.  **Update Usage:** Replace `new MyComponent()` instantiations with declarative `<devtools-widget .widgetConfig=...>` in parent templates.
+5.  **Scoping Styles:** Ensure your CSS file uses the `@scope` block to prevent style leaks:
+    ```css
+    @scope to (devtools-widget > *) {
+      ...
+    }
+    ```
+
+## Key Implementation Details (Gotchas)
+
+### Styling Strategy
+DevTools widgets typically render into Light DOM (the default for `UI.Widget`). To ensure styles are scoped to the component and do not leak into child widgets, wrap your CSS in an `@scope` block:
+
+```css
+/* myWidget.css */
+@scope to (devtools-widget > *) {
+  .my-class { ... }
+}
+```
+
+Then, include the styles in your `DEFAULT_VIEW`:
+
+```ts
+import myWidgetStyles from './myWidget.css.js';
+// ...
+render(html`
+  <style>${myWidgetStyles}</style>
+  <div class="my-widget">...</div>
+`, target);
+```
+
+**Note:** The `{host: input}` option in `render()` is generally **not required** unless you are using specific Shadow DOM patterns that necessitate it. The `@scope` strategy is the preferred method for style isolation in DevTools widgets.
+
+### Legacy Interop & Refs
+*   **Raw Elements:** Use `Lit.Directives.ref` to obtain a reference to a raw `HTMLElement` if needed for imperative APIs (e.g., `splitWidget.installResizer(element)`).
+*   **Child Widgets:** Use `UI.Widget.widgetRef` to obtain the class instance of a child `<devtools-widget>` if you need to call methods on it directly (though declarative data flow is preferred).
+
+### Dependencies
+The `DEFAULT_VIEW` is typically a module-level function. Ensure all dependencies (enums, constants, other components) are imported at the top of the file so they are available in the function scope.
+
+## Step-by-Step Implementation Example
+
+### 1\. Create the Widget File and Styles
+
+Example: `front_end/panels/my_example/MyExampleWidget.ts`.
+
+```css
+/* front_end/panels/my_example/myExampleWidget.css */
+@scope to (devtools-widget > *) {
+  p {
+    color: blue;
+  }
+}
+```
+
+```ts
+// front_end/panels/my_example/MyExampleWidget.ts
+
+import * as Lit from '../../ui/lit/lit.js';
+import * as UI from '../../ui/legacy/legacy.js';
+
+import myExampleWidgetStyles from './myExampleWidget.css.js';
+
+const {html, render, ref} = Lit;
+
+// 1. Define Input data shape. (Assuming Child Widget configuration for completeness)
+export interface ViewInput {
+  title: string;
+  counter: number;
+  onButtonClick: () => void;
+}
+
+// 2. Define Output imperative API shape.
+export interface ViewOutput {
+  focusButton?: () => void;
+}
+
+// 3. Define the View function.
+// clang-format off
+const DEFAULT_VIEW = (input: ViewInput, output: ViewOutput, target: HTMLElement): void => {
+  render(html`
+    <style>${myExampleWidgetStyles}</style>
+    <div class="child-widget">
+      <h3>${input.title}</h3>
+      <p>Counter: ${input.counter}</p>
+      <button @click=${input.onButtonClick} ${ref(el => {
+        if (el) {
+          output.focusButton = () => el.focus();
+        }
+      })}>Increment</button>
+    </div>
+  `, target);
+};
+// clang-format on
+
+// 4. Type alias for the view.
+type View = typeof DEFAULT_VIEW;
+
+// 5. Define the Presenter.
+export class MyExampleWidget extends UI.Widget.Widget {
+  #counter: number = 0;
+
+  // Public field REQUIRED to receive data from a parent.
+  title: string = 'Default Title';
+
+  #view: View;
+  #viewOutput: ViewOutput = {};
+
+  constructor(element?: HTMLElement, view: View = DEFAULT_VIEW) {
+    super(element);
+    this.#view = view;
+  }
+
+  override wasShown(): void {
+    super.wasShown();
+    // Initial render trigger.
+    this.requestUpdate();
+  }
+
+  focus(): void {
+    this.#viewOutput.focusButton?.();
+  }
+
+  #handleButtonClick = (): void => {
+    this.#counter++;
+    this.requestUpdate();
+  }
+
+  override performUpdate(): void {
+    const viewInput = {
+      title: this.title,
+      counter: this.#counter,
+      onButtonClick: this.#handleButtonClick,
+    };
+    this.#view(viewInput, this.#viewOutput, this.contentElement);
+  }
+}
+```
+
+### 2\. Compose Widgets (Parent Widget)
+
+Example: `front_end/panels/parent/ParentWidget.ts`. Demonstrates passing state via `widgetConfig` and a view with no `output`.
+
+```ts
+// front_end/panels/parent/ParentWidget.ts
+
+import * as Lit from '../../ui/lit/lit.js';
+import * as UI from '../../ui/legacy/legacy.js';
+import {MyExampleWidget} from '../my_example/MyExampleWidget.ts';
+
+import parentWidgetStyles from './parentWidgetStyles.css';
+
+const {html, render} = Lit;
+const {widgetConfig} = UI.Widget;
+
+interface ViewInput {
+  title: string;
+  onTitleChange: () => void;
+}
+
+// Parent View
+// clang-format off
+const DEFAULT_VIEW = (input: ViewInput, output: undefined, target: HTMLElement): void => {
+  render(html`
+    <style>${parentWidgetStyles}</style>
+    <div class="parent-container">
+      <h1>Parent Widget</h1>
+      <button @click=${input.onTitleChange}>Change Child Title</button>
+
+      <!-- Pass properties to the child widget. -->
+      <devtools-widget .widgetConfig=${widgetConfig(MyExampleWidget, {title: input.title})}>
+      </devtools-widget>
+    </div>
+  `, target);
+};
+// clang-format on
+
+type View = typeof DEFAULT_VIEW;
+
+// Parent Presenter
+export class ParentWidget extends UI.Widget.Widget {
+  #childTitle: string = 'Initial Title';
+  #view: View;
+
+  constructor(element?: HTMLElement, view: View = DEFAULT_VIEW) {
+    super(element);
+    this.#view = view;
+  }
+
+  override wasShown(): void {
+    super.wasShown();
+    this.requestUpdate();
+  }
+
+  #handleChangeTitleClick = () => {
+    this.#childTitle = `Title set at ${new Date().toLocaleTimeString()}`;
+    this.requestUpdate();
+  }
+
+  override performUpdate(): void {
+    this.#view({
+      title: this.#childTitle,
+      onTitleChange: this.#handleChangeTitleClick,
+    }, undefined, this.contentElement);
+  }
+}
+```
+
+### 3\. Testing Widgets
+
+Testing focuses on the Presenter's logic. The View MUST be replaced by a stub using `createViewFunctionStub`.
+
+* **`describeWithEnvironment`**: Sets up the testing environment.
+* **`createViewFunctionStub`**: Stubs the view to capture `input` data.
+* **`renderElementIntoDOM`**: Attaches the widget to the DOM to trigger lifecycle methods (like `wasShown`).
+* **`view.nextInput`**: A promise that resolves with the next `input` when the widget re-renders.
+* **Simulating Events**: Invoke callbacks directly (e.g., `view.input.onButtonClick()`), do not interact with the DOM.
+
+```ts
+// front_end/panels/my_example/MyExampleWidget.test.ts
+
+import {
+  renderElementIntoDOM,
+} from '../../testing/DOMHelpers.js';
+import {describeWithEnvironment} from '../../testing/EnvironmentHelpers.js';
+import {createViewFunctionStub} from '../../testing/ViewFunctionHelpers.js';
+import * as UI from '../../ui/legacy/legacy.js';
+
+import * as MyExampleWidget from './MyExampleWidget.js';
+
+const {MyExampleWidget} = MyExampleWidget;
+
+describeWithEnvironment('MyExampleWidget', () => {
+  // Helper to set up the widget with a stubbed view.
+  async function createWidget() {
+    // 1. Stub the view function.
+    const view = createViewFunctionStub(MyExampleWidget);
+
+    // 2. Instantiate the widget, injecting the stub.
+    const widget = new MyExampleWidget(undefined, view);
+
+    // 3. Render the widget into the DOM (triggers `wasShown`).
+    widget.markAsRoot();
+    renderElementIntoDOM(widget);
+
+    // 4. Wait for the initial render.
+    await view.nextInput;
+
+    return {view, widget};
+  }
+
+  it('renders with initial state', async () => {
+    const {view} = await createWidget();
+    assert.strictEqual(view.input.counter, 0);
+  });
+
+  it('increments counter on button click', async () => {
+    const {view} = await createWidget();
+
+    // Simulate the click by invoking the callback.
+    view.input.onButtonClick();
+
+    // Wait for the re-render.
+    const finalInput = await view.nextInput;
+
+    assert.strictEqual(finalInput.counter, 1);
+  });
+
+  it('updates its title when a new one is passed in', async () => {
+    const {view, widget} = await createWidget();
+
+    widget.title = 'New Test Title';
+    widget.requestUpdate();
+
+    const finalInput = await view.nextInput;
+    assert.strictEqual(finalInput.title, 'New Test Title');
+  });
+});
+```
+
+## Improving this Guide
+
+This document is a living guide. If you find that the instructions are incomplete, lead to errors, or could be improved, please suggest updates. Your goal is to make this guide as helpful as possible for both human developers and your future AI counterparts.

package/agents/prompts/verification.md

@@ -17,7 +17,8 @@
 
 ## Linting
 
-- `npm run lint` will execute ESLint and StyleLint and report any violations that must be fixed.
+- `npm run lint` will execute ESLint and StyleLint. It will report any violations and automatically fix them where possible.
+- To run the linter on a specific file or directory, you can run `npm run lint -- <PATH>` where `PATH` is a path to a file or directory. This will also automatically fix violations where possible.
 
 ## Best practices
 

package/docs/contributing/README.md

@@ -6,12 +6,11 @@ This page assumes a working Chromium DevTools [checkout and build](../get_the_co
 
 1.   [Quick Start](#Quick-Start)
 2.   [IDE Setup](#IDE-Setup)
-3.   [Design Documents](./design.md)
-4.   [Contributing changes](./changes.md)
-5.   [Issues Guidelines](./issues.md)
-6.   [Settings, Experiments, and Features](./settings-experiments-features.md)
-7.   [Infrastructure](./infrastructure.md)
-8.   [Legal Stuff](#Legal-Stuff)
+3.   [Contributing changes](./changes.md)
+4.   [Issues Guidelines](./issues.md)
+5.   [Settings, Experiments, and Features](./settings-experiments-features.md)
+6.   [Infrastructure](./infrastructure.md)
+7.   [Legal Stuff](#Legal-Stuff)
 
 
 ## Quick Start

package/docs/contributing/changes.md

@@ -1,8 +1,7 @@
 # Contributing changes to Chromium DevTools
 
 See [Get the Code](../get_the_code.md) for details on how to checkout the code,
-and [Design Documents](design.md) for information regarding our design process.
-Also check out [Contributing to
+and check out [Contributing to
 Chromium](https://chromium.googlesource.com/chromium/src/+/main/docs/contributing.md)
 for general information how to contribute to any Chromium project (including
 its developer tools).

package/docs/styleguide/ux/README.md

@@ -16,6 +16,6 @@ user interface.
 
 ## UI reviews
 If you make changes to DevTools UI, make sure to involve us **early**, i.e. already in the
-UI design stage. See also the [Chrome DevTools Design Review Guidelines](../../contributing/design.md#Review-Guidelines)
+UI design stage.
 
 Back to the [Chromium DevTools Documentation](../../README.md).

package/front_end/core/sdk/OverlayModel.ts

@@ -792,10 +792,12 @@ export class OverlayModel extends SDKModel<EventTypes> implements ProtocolProxyA
     return await this.#windowControls.initializeStyleSheetText(url);
   }
 
-  inspectPanelShowRequested(_event: Protocol.Overlay.InspectNodeRequestedEvent): void {
+  inspectPanelShowRequested({backendNodeId}: Protocol.Overlay.InspectPanelShowRequestedEvent): void {
+    this.dispatchEventToListeners(Events.INSPECT_PANEL_SHOW_REQUESTED, backendNodeId);
   }
 
-  inspectedElementWindowRestored(_event: Protocol.Overlay.InspectNodeRequestedEvent): void {
+  inspectedElementWindowRestored({backendNodeId}: Protocol.Overlay.InspectedElementWindowRestoredEvent): void {
+    this.dispatchEventToListeners(Events.INSPECTED_ELEMENT_WINDOW_RESTORED, backendNodeId);
   }
 }
 

package/front_end/core/sdk/RemoteObject.ts

@@ -66,6 +66,11 @@ export abstract class RemoteObject {
     return matches ? parseInt(matches[1], 10) : 0;
   }
 
+  static isEmptyArray(object: RemoteObject|Protocol.Runtime.RemoteObject|Protocol.Runtime.ObjectPreview): boolean {
+    const matches = object.description?.match(descriptionLengthParenRegex);
+    return Boolean(matches?.[1] === '0');
+  }
+
   static unserializableDescription(object: unknown): string|null {
     if (typeof object === 'number') {
       const description = String(object);
@@ -582,7 +587,8 @@ export class RemoteObjectImpl extends RemoteObject {
 
   override isLinearMemoryInspectable(): boolean {
     return this.type === 'object' && this.subtype !== undefined &&
-        ['webassemblymemory', 'typedarray', 'dataview', 'arraybuffer'].includes(this.subtype);
+        ['webassemblymemory', 'typedarray', 'dataview', 'arraybuffer'].includes(this.subtype) &&
+        !RemoteObject.isEmptyArray(this);
   }
 }
 

package/front_end/core/sdk/StorageKeyManager.ts

@@ -56,7 +56,12 @@ export function parseStorageKey(storageKeyString: string): StorageKey {
   // third_party/blink/common/storage_key/storage_key.cc
   const components = storageKeyString.split('^');
   const origin = Common.ParsedURL.ParsedURL.extractOrigin(components[0] as Platform.DevToolsPath.UrlString);
-  const storageKey = {origin, components: new Map<StorageKeyComponent, string>()};
+  const storageKey = {
+    // For file:// URLs, extracting the origin collapses it to "file://".
+    // Node.js uses the full file URL as the StorageKey, so keep the original URL here.
+    origin: origin === 'file://' ? components[0] as Platform.DevToolsPath.UrlString : origin,
+    components: new Map<StorageKeyComponent, string>()
+  };
   for (let i = 1; i < components.length; ++i) {
     storageKey.components.set(components[i].charAt(0) as StorageKeyComponent, components[i].substring(1));
   }

package/front_end/core/sdk/Target.ts

@@ -49,7 +49,7 @@ export class Target extends ProtocolClient.InspectorBackend.TargetBase {
         this.#capabilitiesMask = Capability.BROWSER | Capability.STORAGE | Capability.DOM | Capability.JS |
             Capability.LOG | Capability.NETWORK | Capability.TARGET | Capability.TRACING | Capability.EMULATION |
             Capability.INPUT | Capability.INSPECTOR | Capability.AUDITS | Capability.WEB_AUTHN | Capability.IO |
-            Capability.MEDIA | Capability.EVENT_BREAKPOINTS;
+            Capability.MEDIA | Capability.EVENT_BREAKPOINTS | Capability.DOM_STORAGE;
         if (parentTarget?.type() !== Type.FRAME) {
           // This matches backend exposing certain capabilities only for the main frame.
           this.#capabilitiesMask |=
@@ -92,7 +92,8 @@ export class Target extends ProtocolClient.InspectorBackend.TargetBase {
         this.#capabilitiesMask = Capability.JS | Capability.LOG | Capability.EVENT_BREAKPOINTS | Capability.NETWORK;
         break;
       case Type.NODE:
-        this.#capabilitiesMask = Capability.JS | Capability.NETWORK | Capability.TARGET | Capability.IO;
+        this.#capabilitiesMask =
+            Capability.JS | Capability.NETWORK | Capability.TARGET | Capability.IO | Capability.DOM_STORAGE;
         break;
       case Type.AUCTION_WORKLET:
         this.#capabilitiesMask = Capability.JS | Capability.EVENT_BREAKPOINTS;
@@ -318,5 +319,6 @@ export const enum Capability {
   IO = 1 << 17,
   MEDIA = 1 << 18,
   EVENT_BREAKPOINTS = 1 << 19,
+  DOM_STORAGE = 1 << 20,
   NONE = 0,
 }

package/front_end/entrypoint_template.html

@@ -14,7 +14,11 @@
     }
   }
 </style>
-<meta http-equiv="Content-Security-Policy" content="object-src 'none'; script-src 'self' https://chrome-devtools-frontend.appspot.com">
+<meta
+  http-equiv="Content-Security-Policy"
+  content="default-src 'self' devtools: data:; style-src 'self' 'unsafe-inline' devtools:; object-src 'none'; script-src
+  'self' https://chrome-devtools-frontend.appspot.com; img-src 'self' data:; frame-src * data:; connect-src data:
+  https://chromeuxreport.googleapis.com 'self' devtools:;">
 <meta name="referrer" content="no-referrer">
 <script type="module" src="./entrypoints/%ENTRYPOINT_NAME%/%ENTRYPOINT_NAME%.js"></script>
 <link href="./application_tokens.css" rel="stylesheet">