Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: a8eecb4531dfe6d708d3dca7939798a7faec34a3
https://github.com/WebKit/WebKit/commit/a8eecb4531dfe6d708d3dca7939798a7faec34a3
Author: Per Arne Vollan <[email protected]>
Date: 2026-08-13 (Thu, 13 Aug 2026)
Changed paths:
M Source/WebKit/WebProcess/WebPage/WebPage.cpp
M Tools/TestWebKitAPI/Tests/WebKit/WKWebView/SiteIsolation.mm
Log Message:
-----------
[Site Isolation] google.com: Web content is unresponsive after going back to
search result page
https://bugs.webkit.org/show_bug.cgi?id=321462
rdar://184209098
Reviewed by Basuke Suzuki.
Going back/forward to a page that was suspended into the back/forward cache
under site
isolation could restore an unresponsive page. WebPage::suspendWithFrameItem
removes
the main frame from Page::rootFrames() when suspending, since it's sent to the
main
frame's own process, not just remote subframe processes. Nothing on the restore
path
added it back.
Fix this by not detaching the root frames when receiving the message in the
main frame
process, since it's not required in this case.
Test: SiteIsolation.RestoredPageIsRenderedAfterCrossSiteBFCacheRoundTrip
* Source/WebKit/WebProcess/WebPage/WebPage.cpp:
(WebKit::WebPage::suspendWithFrameItem):
* Tools/TestWebKitAPI/Tests/WebKit/WKWebView/SiteIsolation.mm:
(TestWebKitAPI::(SiteIsolation,
RestoredPageIsRenderedAfterCrossSiteBFCacheRoundTrip)):
(TestWebKitAPI::(SiteIsolation,
RestoredPageWithIframeIsRenderedAfterCrossSiteBFCacheRoundTrip)):
Canonical link: https://commits.webkit.org/319136@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
