RESOLVED FIXED285224
Web processes should only commit history state for navigating frames and their children 
https://bugs.webkit.org/show_bug.cgi?id=285224
Summary Web processes should only commit history state for navigating frames and thei...
Charlie Wolfe
Reported 2024-12-28 18:33:34 PST
Currently, when a frame navigates, the web process creates history state for the entire frame tree to be committed to the UI process. This needs to change with site isolation because a navigating iframe may have parent frames that are out-of-process, for which we cannot synchronously create history state. Instead, when a frame navigates, the web process should only create and commit history state for the navigating frame and its children. If the navigating frame is a child frame, we can use the current item in the UI process's back/forward list to populate the history state for its parent frames.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-12-28 18:33:47 PST
<rdar://problem/142134339>
Charlie Wolfe
Comment 2 2024-12-28 18:37:38 PST
Pull request: https://github.com/WebKit/WebKit/pull/38410
EWS
Comment 3 2025-01-03 10:38:23 PST
Committed 288409@main (9b13b53b41a1): <https://commits.webkit.org/288409@main> Reviewed commits have been landed. Closing PR #38410 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.