[Site Isolation] imported/w3c/web-platform-tests/navigation-timing/navigation-type-post-backforward.html fails on debug build
https://bugs.webkit.org/show_bug.cgi?id=327858
rdar://190247286

Reviewed by Per Arne Vollan.

With UseUIProcessForBackForwardItemLoading, the UI process sends a frame's FrameState to the web
process through two channels: GoToBackForwardItem, when the UI process initiates a traversal, and
PolicyDecision::backForwardFrameState, when a parent being restored delegates the load of a new
child frame to the UI process (dispatchDecidePolicyForBackForwardNavigationAction). However,
decidePolicyForNavigationAction attaches the FrameState to any back/forward policy decision of a
child frame, so for a traversal initiated by the UI process, the web process receives it twice.

The web process creates a HistoryItem from each copy. HistoryController::goToItem passes the first
one to FrameLoader::loadItem, which uses it as both the requested and the provisional history item.
WebFrame::didReceivePolicyDecision then replaces the requested history item with the second one,
while the provisional history item remains the first one. When the target item has form data and
the cache-only load fails, FrameLoader::retryAfterFailedCacheOnlyMainResourceLoad hits
ASSERT(history().provisionalItem() == m_requestedHistoryItem). This happens in
imported/w3c/web-platform-tests/navigation-timing/navigation-type-post-backforward.html, where an
iframe goes back to the result of a POST form submission.

To fix this, do not attach the FrameState to the policy decision when the navigation identifier maps
to a navigation with backForwardTraversalWasDispatched() set, meaning the UI process has already
sent GoToBackForwardItem for it. The delegated child frame load has no navigation identifier, so it
still gets the FrameState. The FrameState is still stored on the navigation, as
continueNavigationInNewProcess needs it when the traversal swaps process.

Covered by existing test: imported/w3c/web-platform-tests/navigation-timing/navigation-type-post-backforward.html

* Source/WebKit/UIProcess/WebPageProxy.cpp:
(WebKit::WebPageProxy::decidePolicyForNavigationAction):

Canonical link: https://commits.webkit.org/324029@main
1 file changed
tree: d3fafb407f4bf4aef7d9b4a68021dfb612af0366
  1. .claude/
  2. .codex/
  3. .gemini/
  4. .github/
  5. Configurations/
  6. JSTests/
  7. LayoutTests/
  8. ManualTests/
  9. metadata/
  10. PerformanceTests/
  11. resources/
  12. Source/
  13. TestExpectations/
  14. Tools/
  15. WebDriverTests/
  16. WebKit.xcworkspace/
  17. WebKitLibraries/
  18. Websites/
  19. .ccls
  20. .clang-format
  21. .dir-locals.el
  22. .editorconfig
  23. .gitattributes
  24. .gitignore
  25. .metadata_never_index
  26. .sourcefilters
  27. .submitproject
  28. .submitproject-append
  29. .submitproject-tools
  30. .swift-format
  31. .wkdev-sdk-version
  32. CMakeLists.txt
  33. CMakePresets.json
  34. Introduction.md
  35. Makefile
  36. Makefile.shared
  37. ReadMe.md
  38. vcpkg-configuration.json
  39. vcpkg.json
ReadMe.md

WebKit

WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, Apple Books, and many other applications. For more information about WebKit, see the WebKit project website.

Trying the Latest

On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.

Reporting Bugs

  1. Search WebKit Bugzilla to see if there is an existing report for the bug you've encountered.
  2. Create a Bugzilla account to report bugs (and comment on them) if you haven't done so already.
  3. File a bug in accordance with our guidelines.

Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.

Getting the Code

Run the following command to clone WebKit's Git repository:

git clone https://github.com/WebKit/WebKit.git WebKit

You can enable git fsmonitor to make many git commands faster (such as git status) with git config core.fsmonitor true

Building WebKit

Building for Apple platforms

Install Xcode and its command line tools if you haven't done so already:

  1. Install Xcode
  2. Install the Xcode Command Line Tools In Terminal, run the command: xcode-select --install
  3. Install the Metal toolchain In Terminal, run the command: xcodebuild -downloadComponent MetalToolchain

Run the following command to build a macOS debug build with debugging symbols and assertions:

Tools/Scripts/build-webkit --debug

For performance testing, and other purposes, use --release instead. If you also need debug symbols (dSYMs), run:

Tools/Scripts/build-webkit --release DEBUG_INFORMATION_FORMAT=dwarf-with-dsym 

Embedded Builds

To build for an embedded platform like iOS, tvOS, or watchOS, pass a platform argument to build-webkit.

For example, to build a debug build with debugging symbols and assertions for embedded simulators:

Tools/Scripts/build-webkit --debug --<platform>-simulator

or embedded devices:

Tools/Scripts/build-webkit --debug --<platform>-device

where platform is ios, tvos or watchos.

Using Xcode

You can open WebKit.xcworkspace to build and debug WebKit within Xcode. Select the “Everything up to WebKit + Tools” scheme to build the entire project.

If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild for both Products and Intermediates.

Building the GTK Port

For production builds:

cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja
ninja
sudo ninja install

For development builds:

Tools/gtk/install-dependencies
Tools/Scripts/update-webkitgtk-libs
Tools/Scripts/build-webkit --gtk --debug

For more information on building WebKitGTK, see the wiki page.

Building the WPE Port

For production builds:

cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja
ninja
sudo ninja install

For development builds:

Tools/wpe/install-dependencies
Tools/Scripts/update-webkitwpe-libs
Tools/Scripts/build-webkit --wpe --debug

Building Windows Port

For building WebKit on Windows, see the WebKit on Windows page.

Running WebKit

With Safari and Other macOS Applications

Run the following command to launch Safari with your local build of WebKit:

Tools/Scripts/run-safari --debug

The run-safari script sets the DYLD_FRAMEWORK_PATH environment variable to point to your build products, and then launches /Applications/Safari.app. DYLD_FRAMEWORK_PATH tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks.

To run other applications with your local build of WebKit, run the following command:

Tools/Scripts/run-webkit-app <application-path>

iOS Simulator

Run the following command to launch iOS simulator with your local build of WebKit:

run-safari --debug --ios-simulator

In both cases, if you have built release builds instead, use --release instead of --debug.

To run other applications, for example MobileMiniBrowser, with your local build of WebKit, run the following command:

Tools/Scripts/run-webkit-app --debug --iphone-simulator <application-path>

Using Xcode

Open WebKit.xcworkspace, select intended scheme such as MobileMiniBrowser and an iOS simulator as target, click run.

Linux Ports

If you have a development build, you can use the run-minibrowser script, e.g.:

run-minibrowser --debug --wpe

Pass one of --gtk, --jsc-only, or --wpe to indicate the port to use.

Contribute

Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.