Bug 242266 - Align with spec on SharedArrayBuffer availability (COOP+COEP) and postMessage
Summary: Align with spec on SharedArrayBuffer availability (COOP+COEP) and postMessage
Status: RESOLVED DUPLICATE of bug 243764
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-07-01 14:30 PDT by Sam Sneddon [:gsnedders]
Modified: 2022-08-11 17:31 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Sneddon [:gsnedders] 2022-07-01 14:30:55 PDT
Brent accidentally sent me down a wormhole that led me here.

In short, we should match the spec as of https://github.com/whatwg/html/pull/4734; this means (tl;dr):

SharedArrayBuffer is available, though the constructor is not, regardless of COOP+COEP, but cannot be sent via postMessage.

With suitable restrictive COOP+COEP headers, the SharedArrayBuffer constructor is available and can be sent via postMessage.

See https://wpt.fyi/results/html/infrastructure/safe-passing-of-structured-data?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned

This also explains Bug 220364.
Comment 1 Radar WebKit Bug Importer 2022-07-01 14:31:07 PDT
<rdar://problem/96314637>
Comment 2 Sam Sneddon [:gsnedders] 2022-07-01 14:54:38 PDT
(In reply to Sam Sneddon [:gsnedders] from comment #0)
> Brent accidentally sent me down a wormhole that led me here.

Specifically, it led to me writing https://github.com/web-platform-tests/wpt/pull/34678 because they don't pass with our current restrictions (as it turns out, that change is also wrong because I didn't make them load over HTTPS, but that's a problem for next week).
Comment 3 Yusuke Suzuki 2022-08-11 17:31:25 PDT
Fixed in bug 243764

*** This bug has been marked as a duplicate of bug 243764 ***