Bug 285054
| Summary: | FrameState and its UI process-side wrapper should not require duplicate frame trees | ||
|---|---|---|---|
| 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
WebBackForwardListFrameItem is a UI process-side wrapper for FrameState, and both maintain child objects that are expected to match. So, when a child HistoryItem is created or destroyed in the web process, logic is needed to update both WebBackForwardListFrameItem and FrameState. To simplify this, we should clear FrameState::children when storing it in the UI process and only have WebBackForwardListFrameItem manage its children.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/141856040>
Charlie Wolfe
Pull request: https://github.com/WebKit/WebKit/pull/38302
EWS
Committed 288245@main (0cbb972550c2): <https://commits.webkit.org/288245@main>
Reviewed commits have been landed. Closing PR #38302 and removing active labels.