Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: e9efe850d15ee55b799ce20e8b53a3e9c06116e5
https://github.com/WebKit/WebKit/commit/e9efe850d15ee55b799ce20e8b53a3e9c06116e5
Author: Per Arne Vollan <[email protected]>
Date: 2025-12-06 (Sat, 06 Dec 2025)
Changed paths:
M Source/WebKit/UIProcess/RemotePageProxy.cpp
M Source/WebKit/UIProcess/WebPageProxy.cpp
M Source/WebKit/UIProcess/WebPageProxy.h
Log Message:
-----------
[Site Isolation] WebContent processes in visible iframes are not always
getting a foreground assertion
https://bugs.webkit.org/show_bug.cgi?id=303660
rdar://165941185
Reviewed by Sihui Liu.
Local debugging shows that WebContent processes in visible iframes are not
always getting a foreground assertion.
This is because a visible activity is not always taken on them. Visible
activities are taken when the activity
state of the page changes, but this is not deterministic. This can be addressed
by always taking a visible
activity on the WebContent process when creating a RemotePageProxy object.
* Source/WebKit/UIProcess/RemotePageProxy.cpp:
(WebKit::RemotePageProxy::injectPageIntoNewProcess):
* Source/WebKit/UIProcess/WebPageProxy.cpp:
(WebKit::WebPageProxy::takeActivitiesOnRemotePage):
* Source/WebKit/UIProcess/WebPageProxy.h:
Canonical link: https://commits.webkit.org/304054@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
