Bug 286334
| Summary: | [Site Isolation] Creating an iframe while updating the history state of its parent causes a new back/forward item to be created | ||
|---|---|---|---|
| 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 | ||
Charlie Wolfe
When a root child frame expects its initial history state to be committed, we store a WebBackForwardListFrameItem on its WebFrameProxy and add a child to it when the history item is committed. If the WebBackForwardListFrameItem is destroyed before the item is committed, a new item is added to the back-forward list instead of adding a frame to the existing item.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/143359188>
Charlie Wolfe
Pull request: https://github.com/WebKit/WebKit/pull/39359
EWS
Committed 289228@main (cbb8b220c0f1): <https://commits.webkit.org/289228@main>
Reviewed commits have been landed. Closing PR #39359 and removing active labels.