> In line with other browsers, Chrome 64 will disable SharedArrayBuffer and modify the behaviour of other APIs such as performance.now, to help reduce the efficacy of speculative side-channel attacks. This is a temporary measure until other mitigations are in place.
Is chrome or edge affected?
Should the SharedArrayBuffer mdn page be updated; or maybe moz://a will fix it quickly enough to allow it on by default again.
By the looks of it, this will affect a lot of webgl code.
[0]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...