Skip to content

Fix storage-access-api/requestStorageAccess-web-socket.sub.https.window.html to properly respect same-origin policy #1213

@cfredric

Description

@cfredric

Test List

https://wpt.fyi/results/storage-access-api/requestStorageAccess-web-socket.sub.https.window.html?label=master&label=experimental&aligned&view=interop&q=label%3Ainterop-2025-storageaccess

Rationale

This test (specifically the "WebSocket inherits storage access" subtest) aims to test a scenario where an iframe (which has requested storage access) opens a websocket connection to a websocket server that is same-origin with the iframe's source. However, the wpt framework runs all websockets on different ports than the HTTP servers run on, so there's no way to construct this scenario within the wpt framework.

Thus, the scenario under test is actually cross-origin, and we should change the final assert_true to be assert_false accordingly.

(For reference: the spec was changed to adhere to the SOP more strictly in privacycg/storage-access#213, at which point this test became incorrect.)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions