306075 2026-01-22 16:12:47 -0800 [Site Isolation] create proxying version of PageAgent based in UIProcess 2026-05-25 21:36:39 -0700 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build All All RESOLVED FIXED InRadar P2 Normal --- 308895 308896 308897 308898 308899 308900 309222 309223 1 bburg bburg bburg inspector-bugzilla-changes webkit-bug-importer oldest_to_newest 2174293 0 bburg 2026-01-22 16:12:47 -0800 Design sketch: 1. Create ProxyingPageAgent in UIProcess, owned by WebPageInspectorController. When site-isolation is enabled, this domain takes over dispatch of the Page domain commands coming from the frontend. ProxyingPageAgent maintains the same PageTarget-based API for forward and backward compatibility with all frontends. 2. Create new PageAgentProxy in WebProcess, which duplicates the "instrumenting" of PageAgent including InspectorInstrumentation hooks and a slot in WebCore::InstrumentingAgents. Events (domContentLoaded, etc) get forwarded to the agent in UIProcess and dispatched out to the frontend. An IPC interface between ProxyingPageAgent and PageAgentProxy will provide a way to collect frame info from each WebProcess as needed. Enablement is bootstrapped via IPC::Messages::WebInspectorBackend:EnablePageInstrumentation. 3. Keep legacy PageAgent implementation around as LegacyPageAgent. We'll need to maintain it in the short-term as a fallback for ProxyingPageAgent, and in the longer-term for WebKitLegacy support. It will continue to live only in top-document's WebProcess, attached to PageInspectorController. Commands not yet implemented for ProxyingPageAgent will be forwarded to the LegacyPageAgent. 2174294 1 webkit-bug-importer 2026-01-22 16:13:08 -0800 <rdar://problem/168716398> 2192808 2 bburg 2026-03-23 10:46:19 -0700 Pull request: https://github.com/WebKit/WebKit/pull/61177 2214005 3 ews-feeder 2026-05-25 21:36:37 -0700 Committed 313867@main (6fd4b1f654c6): <https://commits.webkit.org/313867@main> Reviewed commits have been landed. Closing PR #61177 and removing active labels.