SharedArray and Atomics examples don't work!

[kevmoo]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/and

What specific section or headline is this issue about?

Try it

What information was incorrect, unhelpful, or incomplete?

Example fails because SharedArrayBuffer is not available

What did you expect to see?

Demo should work!

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp

https://developer.mozilla.org/en-US/docs/Web/API/crossOriginIsolated is false

Should either update the hosting story or delete the example 🤷

MDN metadata

Page report details

• Folder: en-us/web/javascript/reference/global_objects/atomics/and
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/and
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/javascript/reference/global_objects/atomics/and/index.md
• Last commit: b855776
• Document last modified: 2021-11-23T19:39:21.000Z

[jzombie]

@kevmoo Which browser and what version are you using?

---

Edit: Yeah, it doesn't work in Chrome either.

[kevmoo]

I'd suggest looking through all related examples – they are likely all broken.

[hamishwillee]

Yes, this requires the server to set:

Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp

I have raised mdn/interactive-examples#2105 to see if this can be done by the interactive examples.

In the meantime the SharedArrayBuffer docs need to be updated to better highlight this issue. Specifically, I THINK we should:

1. Update the BCD with a subfeature for the security requirements to highlight the version. @queengooborg Would it make sense to do this as a subfeature of the constructor?
2. Update the note in constructor header to make it less chrome specific and point to the limitation in the bcd
3. In the top level doc not the restriction in the header.

[queengooborg]

If it's consistent across multiple browser engines, or is required by the spec, then yeah, I'd say a BCD subfeature is the way to go!

[Josh-Cena]

This seems to be an issue anywhere but in content. Where should we track this? BCD? interactive-examples? Yari?

[hamishwillee]

This seems to be an issue anywhere but in content.

@Josh-Cena I don't understand what you mean by the above statement

I missed the response from @queengooborg . I believe we need to check the spec and see if this security requirement is defined. If not, work out where it comes from and go from there.

[Josh-Cena]

The requirement is defined. It's also present in our content. (See also #3489) The only problem here is that our interactive example infra does not serve it with the correct header, which seems more like an infrastructure issue than a content issue. If we want to track the documentation support for COOP and COEP (including both removal of the notion of "planned changes" and incorporation of BCD), we can do that in #3489.

[hamishwillee]

@Josh-Cena Thanks.

So yes, this specific bug is an infrastructure issue, which will be fixed (hopefully) by mdn/interactive-examples#2105

Yes, #3489 is a more logical place to track BCD and doc fixes.

[Josh-Cena]

OK, let's track it separately in mdn/interactive-examples#2105 and #3489 instead.