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
Recently upgraded to version 5.3.2 and now getting the following warning in Chrome:
It seems that in msgpack5.js there is code that checks for SharedArrayBuffer, but it doesn't actually use it as part of the functionality.
Chrome version 91 (yet to be released) will apparently require a web page to be cross-origin isolated, requiring the use of new response headers, etc. Only sites modified as such will be able to use SharedArrayBuffer.
I have tried our site in Chrome DEV version 91, and all appears fine - in fact, it seems that the msgpack library no longer makes any checks on SharedArrayBuffer in this context.
May I please ask if there is an intention to use SharedArrayBuffer in earnest in the future, or will the msgpack5 library always gracefully "degrade"?
Many thanks,
Nick
The text was updated successfully, but these errors were encountered:
Hi!
Recently upgraded to version 5.3.2 and now getting the following warning in Chrome:
It seems that in msgpack5.js there is code that checks for SharedArrayBuffer, but it doesn't actually use it as part of the functionality.
Chrome version 91 (yet to be released) will apparently require a web page to be cross-origin isolated, requiring the use of new response headers, etc. Only sites modified as such will be able to use SharedArrayBuffer.
I have tried our site in Chrome DEV version 91, and all appears fine - in fact, it seems that the msgpack library no longer makes any checks on SharedArrayBuffer in this context.
May I please ask if there is an intention to use SharedArrayBuffer in earnest in the future, or will the msgpack5 library always gracefully "degrade"?
Many thanks,
Nick
The text was updated successfully, but these errors were encountered: