-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider enabling cross origin isolated #334
Comments
At this point, I don't think we're doing this for v3. Perhaps v3.1? |
|
Chrome 123.0.6312.107Before28.8 ± 1.5 After28.8 ± 1.8 Firefox 124.0.2Before29.7 ± 1.8 After29.4 ± 1.7 Safari 17.4 (19618.1.15.11.12)Before30.9 ± 1.3 After30.7 ± 1.9 |
JetStream resultsChromeBefore351.786 After348.701 FirefoxBefore243.390 After246.106 SafariBefore355.951 After359.015 |
MotionMark resultsChromeBefore5883.73 @ 60fps ±3.31% After5821.87 @ 60fps ±5.49 FirefoxBefore1890.53 @ 60fps ±9.10% After1927.66 @ 60fps ±2.15% SafariBefore5759.77 @ 60fps ±1.21% After5827.52 @ 60fps ±2.68% |
We should consider enabling cross origin isolated in browserbench.org so that
performance.now
will be high precision. See https://web.dev/articles/coop-coep for details.The text was updated successfully, but these errors were encountered: