Skip to content

Web Inspector Site Isolation Explainer v2#133

Open
burg wants to merge 6 commits intoWebKit:mainfrom
burg:eng/bburg/1209-inspector-site-isolation
Open

Web Inspector Site Isolation Explainer v2#133
burg wants to merge 6 commits intoWebKit:mainfrom
burg:eng/bburg/1209-inspector-site-isolation

Conversation

@burg
Copy link

@burg burg commented Dec 10, 2025

This is a draft and will be revised prior to pushing to prod.

(removed unhelpful commit template for now)

Second editing session adds more details about Target system.
@burg burg force-pushed the eng/bburg/1209-inspector-site-isolation branch from 4adf9cc to 4842b9a Compare December 11, 2025 05:15
…cture

Rewrites SiteIsolationExplainer.md with a complete, accurate description of
the Web Inspector SI design: frame target lifecycle, BackendDispatcher fallback
chain, the split UIProcess/WebProcess design for Network and Page domains
(ProxyingNetworkAgent + NetworkAgentProxy), and open questions.

Also adds a Web Inspector cross-reference section to SiteIsolation.md.
@burg burg changed the title [WIP] Initial dump for Web Inspector Site Isolation Explainer Web Inspector Site Isolation Explainer v2 Feb 25, 2026
burg added 4 commits February 26, 2026 15:38
…cs, Security section

- Rename to post-rename names: PageInspectorTargetProxy,
  FrameInspectorTargetProxy, FrameInspectorTarget,
  UIProcessForwardingFrontendChannel
- Fix target type from WebPage to Page in Mode 1 and diagram
- Replace hierarchy language with peer semantics in Mode 2
- Update code snippets to didCreateFrame/willDestroyFrame API
- Add Security: Inspector-Only IPC Interfaces section explaining
  dynamic IPC receiver registration, conditional instrumentation,
  ordering guarantees, and per-page scoping
- Update Compatibility section to avoid "sub-targets" framing
- Add proxy agent source files to Key Source Files table
- Add table of contents with anchor links for all major sections
- Remove BJB> working notes (phases bug links, domain placeholder,
  architect planning request)
Added per-domain migration status tables for all 19 inspector domains,
covering both per-frame (11 domains) and octopus (8 domains) patterns.
Added migration priority ordering and key architectural risks (Debugger
single-VM problem, DOM cross-frame traversal, CSS coupling, Network
RequestId collision).
|--------|--------|-------|
| **Console** | Done | `FrameConsoleAgent` landed; reference implementation for all per-frame agents |
| **Runtime** | In progress | `FrameRuntimeAgent` (PR [#59021](https://github.com/WebKit/WebKit/pull/59021)) |
| **Debugger** | Not started | Blocked on [bug 298909](https://bugs.webkit.org/show_bug.cgi?id=298909); single-debugger-multiple-agents challenge |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the current status of bug 298909? Is it being actively worked on?

The **Browser** domain already lives entirely in `WebPageInspectorController` and requires
no migration.

### Migration Priority Order
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we explain a bit about how the order is decided? (I guess it's user impact plus dependency)


---

## Key Source Files
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May also include test files (or have a test section to talk about the testing plan, current pass rate with SI, cross-site frame coverage, etc)


---

## Key Risks and Architectural Challenges
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For these known risks, do we already have solution candidates? Or is it still in the exploratory phase (don't know how to resolve yet)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants