Closed Bug 1630877 Opened 4 years ago Closed 4 years ago

Audio worklets should only have a SharedArrayBuffer global property if COOP/COEP permits it

Categories

(Core :: Web Audio, defect, P1)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: Waldo, Assigned: tt)

References

Details

Bug 1624266 will cause the global SharedArrayBuffer property to only be present if a page is served with COOP/COEP headers that opt into cross-site isolation. This needs to be applied to audio worklets, too -- by changing the value assigned to defineSharedArrayBufferConstructor in AudioWorkletGlobalScope.cpp. (I/we haven't bothered doing it there because audio worklets aren't implemented yet [right?].)

(In reply to Jeff Walden [:Waldo] from comment #0)

(I/we haven't bothered doing it there because audio worklets aren't implemented yet [right?].)

We have finished implementation and we're shipping in 76. Do you want to do it? I can certainly do it if you point me to an example, if that helps.

Priority: -- → P1
Blocks: 1606624
See Also: → 1624266

Please apologize the somewhat aggressive needinfo-ing, but the hope was to ship this in 78 and that branches a week from now if I'm reading https://wiki.mozilla.org/Release_Management/Calendar correctly. What are the chances of making that?

(On the other hand, given that it's not a security issue (postMessage() throws after all) and audio worklets are very new, I somewhat doubt we would hit any of the potential compatibility issues we're hiding globalThis.SharedArrayBuffer for. So it might be okay to ship and address this later.)

Flags: needinfo?(padenot)
Flags: needinfo?(karlt)

I did that in D71536 so I guess we can close this bug when Bug 1624266 is fixed or move the patch to here.

Flags: needinfo?(padenot)
Flags: needinfo?(karlt)
Depends on: 1624266
Assignee: nobody → ttung
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.