RESOLVED FIXED321822
[Site Isolation] Web Inspector: Don't report duplicate Page.frameNavigated events per frame commit 
https://bugs.webkit.org/show_bug.cgi?id=321822
Summary [Site Isolation] Web Inspector: Don't report duplicate Page.frameNavigated ev...
Qianlang Chen
Reported 2026-08-14 16:43:01 PDT
A frame commit reports Page.frameNavigated twice, once from the in-process InspectorPageAgent and once from the per-frame PageAgentProxy, and the frontend's handling of the second report re-initializes the frame -- discarding the child frames, resources, and execution contexts it already learned about. The worst case is nested iframes, where a parent's duplicate arriving after its children attached detachesa live subtree Address this to prevent breakages when we enable old and new Page domains at the same time, in Bug 321738 (rdar://184867249)
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2026-08-14 16:43:07 PDT
<rdar://problem/184962162>
Qianlang Chen
Comment 2 2026-08-14 16:48:14 PDT
https://github.com/WebKit/WebKit/pull/71672
EWS
Comment 3 2026-09-01 14:35:52 PDT
Committed 320271@main (42583e7e49eb): <https://commits.webkit.org/320271@main> Reviewed commits have been landed. Closing PR #71672 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.