2 ms·
Fixed by these: - Site Isolation (https://www.chromium.org/Home/chromium-security/site-isolation https://www.chromium.org/Home/chromium-security/site-isolati..
by feross 8y ago
Fixed by these:
- Site Isolation (https://www.chromium.org/Home/chromium-security/site-isolation https://www.chromium.org/Home/chromium-security/site-isolati...)
- Cross-Origin Read Blocking (https://www.chromium.org/Home/chromium-security/corb-for-developers https://www.chromium.org/Home/chromium-security/corb-for-dev...)
- bzbarsky 8y agoIt's not fully fixed by those, for what it's worth; I'm happy to provide examples outside a public venue. Chrome just decided it doesn't care about the security holes it's creating in websites. Other browsers are working on rolling out other mitigations they consider security-critical before being OK with re-enabling SharedArrayBuffer.