NEW299830
REGRESSION(300617@main): [macOS] imported/w3c/web-platform-tests/storage-access-api/hasStorageAccess-insecure.sub.window.html is flaky 
https://bugs.webkit.org/show_bug.cgi?id=299830
Summary REGRESSION(300617@main): [macOS] imported/w3c/web-platform-tests/storage-acce...
Marta Darbinyan
Reported 2025-09-29 16:11:19 PDT
The following test became flaky after 300617@main both in Release and Debug. imported/w3c/web-platform-tests/storage-access-api/hasStorageAccess-insecure.sub.window.html PASS [same-origin-frame] document.hasStorageAccess() should be supported on the document interface PASS [same-origin-frame] document.hasStorageAccess() should be disallowed in insecure contexts PASS [same-origin-frame] document.hasStorageAccess() should reject in a document that isn't fully active. +PASS [cross-origin-frame] document.hasStorageAccess() should be supported on the document interface +PASS [cross-origin-frame] document.hasStorageAccess() should be disallowed in insecure contexts +PASS [cross-origin-frame] document.hasStorageAccess() should reject in a document that isn't fully active. PASS [nested-same-origin-frame] document.hasStorageAccess() should be supported on the document interface PASS [nested-same-origin-frame] document.hasStorageAccess() should be disallowed in insecure contexts PASS [nested-same-origin-frame] document.hasStorageAccess() should reject in a document that isn't fully active. -PASS [cross-origin-frame] document.hasStorageAccess() should be supported on the document interface -PASS [cross-origin-frame] document.hasStorageAccess() should be disallowed in insecure contexts -PASS [cross-origin-frame] document.hasStorageAccess() should reject in a document that isn't fully active. PASS [nested-cross-origin-frame] document.hasStorageAccess() should be supported on the document interface PASS [nested-cross-origin-frame] document.hasStorageAccess() should be disallowed in insecure contexts PASS [nested-cross-origin-frame] document.hasStorageAccess() should reject in a document that isn't fully active. Test history: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fstorage-access-api%2FhasStorageAccess-insecure.sub.window.html Test result: https://ews-build.webkit.org/#/builders/122/builds/38481
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2025-09-29 16:11:53 PDT
<rdar://problem/161605161>
EWS
Comment 2 2025-09-30 11:28:24 PDT
Test gardening commit 300765@main (c66650e9a65e): <https://commits.webkit.org/300765@main> Reviewed commits have been landed. Closing PR #51572 and removing active labels.
Alexey Proskuryakov
Comment 3 2025-09-30 15:44:05 PDT
This probably uncovered the issue by making the test run more correctly, and didn't cause it.
Jonathan Bedard
Comment 4 2025-10-01 14:15:23 PDT
Can we just add `await` before each of the `RunTestsInIFrame` calls? I think that's an async testing call, it's not surprising that reliable ordering is an issue.
Sam Sneddon [:gsnedders]
Comment 5 2025-10-07 13:26:28 PDT
This is again bug 252268, where we're having issues because we're relying on things that testharness.js API contract doesn't guarantee.
Diego De La Toba
Comment 6 2026-03-04 12:21:14 PST
imported/w3c/web-platform-tests/storage-access-api/hasStorageAccess-insecure.sub.window.html is a also flaky on iOS release, gardening.
Diego De La Toba
Comment 7 2026-03-04 13:08:01 PST
Pull request: https://github.com/WebKit/WebKit/pull/59914
EWS
Comment 8 2026-03-04 13:09:55 PST
Test gardening commit 308656@main (2e516427321c): <https://commits.webkit.org/308656@main> Reviewed commits have been landed. Closing PR #59914 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.