Bug 285224
| Summary: | Web processes should only commit history state for navigating frames and their children | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Charlie Wolfe <charliew> |
| Component: | History | Assignee: | Charlie Wolfe <charliew> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 285442 | ||
| Bug Blocks: | |||
Charlie Wolfe
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
<rdar://problem/142134339>
Charlie Wolfe
Pull request: https://github.com/WebKit/WebKit/pull/38410
EWS
Committed 288409@main (9b13b53b41a1): <https://commits.webkit.org/288409@main>
Reviewed commits have been landed. Closing PR #38410 and removing active labels.