Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 09efe9e1f6b74cfe8d86403c76a22cc271567456
      
https://github.com/WebKit/WebKit/commit/09efe9e1f6b74cfe8d86403c76a22cc271567456
  Author: Adrian Taylor <[email protected]>
  Date:   2026-09-17 (Thu, 17 Sep 2026)

  Changed paths:
    M Source/WebKit/UIProcess/ProvisionalPageProxy.cpp
    M Source/WebKit/UIProcess/ProvisionalPageProxy.h
    M Source/WebKit/UIProcess/WebBackForwardList.cpp
    M Source/WebKit/UIProcess/WebBackForwardList.h
    M Source/WebKit/UIProcess/WebBackForwardList.swift
    M Source/WebKit/UIProcess/WebBackForwardListSwiftUtilities.h
    M Source/WebKit/UIProcess/WebPageProxy.cpp
    M Source/WebKit/UIProcess/WebPageProxy.h

  Log Message:
  -----------
  Fix backForwardGoToItemShared connection
https://bugs.webkit.org/show_bug.cgi?id=324451
rdar://187692326

Reviewed by Richard Robinson.

BackForwardGoToItem can arrive at ProvisionalPageProxy, on the provisional
process's connection, but the check was marked against
legacyMainFrameProcess(). Marking a connection that is not the one dispatching
sets m_didReceiveInvalidMessage outside Connection::dispatchMessage's
save/restore of it, so didReceiveInvalidMessage() never runs and the sender is
not terminated. It also asserts in debug builds.

Pass the sending connection down instead. connectionForProcess() existed only
for the old workaround, so it goes too.

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



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

Reply via email to