Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 613afab6d7a2c9ff3b3a747c9ffe7f91a81b321d
https://github.com/WebKit/WebKit/commit/613afab6d7a2c9ff3b3a747c9ffe7f91a81b321d
Author: Per Arne Vollan <[email protected]>
Date: 2026-09-19 (Sat, 19 Sep 2026)
Changed paths:
M Source/WebCore/dom/Document.cpp
M Source/WebCore/dom/Document.h
M Source/WebCore/page/RemoteFrame.cpp
M Tools/TestWebKitAPI/Tests/WebKit/WKWebView/SiteIsolation.mm
Log Message:
-----------
[Site Isolation] Stop button never turns back into reload button on certain
pages
https://bugs.webkit.org/show_bug.cgi?id=324567
rdar://185828742
Reviewed by Sihui Liu.
When the main frame process receives a message that a load has finished in
another process,
we need to call FrameLoader::checkLoadComplete. It is not sufficient to call
FrameLoader::checkCompleted as we currently do. This is because
FrameLoader::checkCompleted
does not trigger the WebContent process to notify the UI process that the load
finished for
the frame when it returns early due to m_isComplete being true.
New API test:
SiteIsolation.MainFrameFinishesLoadWithCrossOriginAndSameOriginIframes
* Source/WebCore/dom/Document.cpp:
(WebCore::Document::checkLoadComplete):
* Source/WebCore/dom/Document.h:
* Source/WebCore/page/RemoteFrame.cpp:
(WebCore::RemoteFrame::didFinishLoadInAnotherProcess):
* Tools/TestWebKitAPI/Tests/WebKit/WKWebView/SiteIsolation.mm:
(TestWebKitAPI::(SiteIsolation,
MainFrameFinishesLoadWithCrossOriginAndSameOriginIframes)):
Canonical link: https://commits.webkit.org/321459@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
