Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: e12578547350f9e6b316afaf52bd90e88c0a7a70
https://github.com/WebKit/WebKit/commit/e12578547350f9e6b316afaf52bd90e88c0a7a70
Author: Roberto Rodriguez <[email protected]>
Date: 2026-04-15 (Wed, 15 Apr 2026)
Changed paths:
M
LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt
M
LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load.html
M LayoutTests/platform/ios-site-isolation/TestExpectations
M LayoutTests/platform/mac-site-isolation/TestExpectations
Log Message:
-----------
[Site Isolation] CSP frame-src-cross-origin-load.html test fails with site
isolation due to incorrect onload assignment
https://bugs.webkit.org/show_bug.cgi?id=312315
rdar://174778663
Reviewed by Rupin Mittal.
Test http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load.html
uses iframe.onload = loadEvent(),
which invokes loadEvent immediately instead of only assigning it as a handler.
Without site isolation this happened
to be passing because the expected output was aligning with the buggy test
execution. With site isolation the iframe
loads in a separate process, and the extra IPC latency means a console message
arrives after the test has already
finalized, causing a mismatch with the expected output.
Fix by assigning the iframe.onload handler correctly and update the expected
output to reflect the correct load ordering.
*
LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load-expected.txt:
*
LayoutTests/http/tests/security/contentSecurityPolicy/frame-src-cross-origin-load.html:
* LayoutTests/platform/ios-site-isolation/TestExpectations:
* LayoutTests/platform/mac-site-isolation/TestExpectations:
Canonical link: https://commits.webkit.org/311290@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
