You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filing this as a tracking issue for the future that can also be used as a reference from tests (see web-platform-tests/wpt#22358). The idea is to eventually unconditionally expose the SharedArrayBuffer constructor.
#4732 (comment) has rationale for why that is not done from the get-go.
The text was updated successfully, but these errors were encountered:
pullbot
pushed a commit
to luojiguicai/chromium
that referenced
this issue
Apr 22, 2021
The SharedArrayBuffer constructor is not exposed anymore in non
cross-origin-isolated contexts. Trying to use it throws, instead of
raising a warning. For creating a SharedArrayBuffer and testing the
devtools issue, we need to use the trick from
whatwg/html#5380.
Bug: 1194226
Change-Id: I622e5857af4de89e726aadc3731bc5a0df0e91f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2843329
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875074}
mjfroman
pushed a commit
to mjfroman/moz-libwebrtc-third-party
that referenced
this issue
Oct 14, 2022
The SharedArrayBuffer constructor is not exposed anymore in non
cross-origin-isolated contexts. Trying to use it throws, instead of
raising a warning. For creating a SharedArrayBuffer and testing the
devtools issue, we need to use the trick from
whatwg/html#5380.
Bug: 1194226
Change-Id: I622e5857af4de89e726aadc3731bc5a0df0e91f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2843329
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875074}
GitOrigin-RevId: 5bbe2a305de0e9dabff0fed4c4a347de657e35be
Filing this as a tracking issue for the future that can also be used as a reference from tests (see web-platform-tests/wpt#22358). The idea is to eventually unconditionally expose the SharedArrayBuffer constructor.
#4732 (comment) has rationale for why that is not done from the get-go.
The text was updated successfully, but these errors were encountered: