[webkit-changes] [WebKit/WebKit] da1153: [Site Isolation] Main frame history state may be i...

[Charlie Wolfe]

  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: da11536420a63001e81fbd98f6b546a1848bc8a7
      https://github.com/WebKit/WebKit/commit/da11536420a63001e81fbd98f6b546a1848bc8a7
  Author: Charlie Wolfe <charliew at apple.com>
  Date:   2025-02-19 (Wed, 19 Feb 2025)

  Changed paths:
    A LayoutTests/http/tests/site-isolation/history/add-iframes-and-navigate-mainframe-expected.txt
    A LayoutTests/http/tests/site-isolation/history/add-iframes-and-navigate-mainframe.html
    M Source/WebKit/UIProcess/WebPageProxy.cpp

  Log Message:
  -----------
  [Site Isolation] Main frame history state may be incorrectly created when navigating during iframe creation
https://bugs.webkit.org/show_bug.cgi?id=287998
rdar://145164046

Reviewed by Alex Christensen.

Site Isolation introduces an unavoidable race condition where the history state committed by a web
process may have been created for a frame that the UI process has already destroyed. When this happens,
we should return early instead of adding an incorrect back/forward item.

* LayoutTests/http/tests/site-isolation/history/add-iframes-and-navigate-mainframe-expected.txt: Added.
* LayoutTests/http/tests/site-isolation/history/add-iframes-and-navigate-mainframe.html: Added.
* Source/WebKit/UIProcess/WebPageProxy.cpp:
(WebKit::WebPageProxy::backForwardAddItemShared):

Canonical link: https://commits.webkit.org/290673@main



To unsubscribe from these emails, change your notification settings at https://github.com/WebKit/WebKit/settings/notifications