Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 5ae613d501a46f8c7e5620868efc82185591d0a5
      
https://github.com/WebKit/WebKit/commit/5ae613d501a46f8c7e5620868efc82185591d0a5
  Author: Basuke Suzuki <[email protected]>
  Date:   2026-09-28 (Mon, 28 Sep 2026)

  Changed paths:
    M LayoutTests/platform/ios-site-isolation/TestExpectations

  Log Message:
  -----------
  [Site Isolation] Eight Navigation API BFCache tests no longer fail under Site 
Isolation on iOS
https://bugs.webkit.org/show_bug.cgi?id=325323
rdar://188433652

Reviewed by Sihui Liu.

All eight pass under Site Isolation on the iOS Simulator, in Debug and in 
Release. Debug reported
every one of them as "Expected to fail, but passed" and held at 24/24 over 
--iterations=3; Release
did the same inside a full navigation-api suite run of 491 tests. None of the 
entries carries a
configuration qualifier, so each claimed both configurations and both are 
contradicted.

The runs were not vacuous. focus-reset/basic.html and 
focus-reset/multiple-intercept.html, which
platform/ios marks [ Failure ], did fail as expected in the same invocations, 
so the harness was
reporting failures rather than rubber-stamping.

The entries exist only here, so removing them makes the tests expected to pass. 
This is the iOS
counterpart of 321645@main, which removed the equivalent stale 
mac-site-isolation entry; with both
gone the Navigation API layout tests have no remaining expectation debt under 
Site Isolation.

Two adjacent findings are left alone, for separate bugs: 
loading/preloader-template.html on the line
above also passes, and 
navigate-event/signal-abort-window-stop-after-intercept.html passes despite
platform/ios marking it [ Timeout Crash ] (rdar://178006888).

Covered by existing tests.

* LayoutTests/platform/ios-site-isolation/TestExpectations:

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



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

Reply via email to