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
{{ message }}
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
Sometimes 60fps is unreasonable for a given page and device, so perhaps we shouldn't always strive to achieve that. Also, 60fps during page load (with heavy style recalc, layout, JS execution, etc.) is usually unreasonable even for more powerful devices.
Perhaps we should always load pages at 30fps, and then switch into 60fps once we've detected that it's taking less than 16.6ms of CPU time to generate each frame.
The text was updated successfully, but these errors were encountered:
(As noted in #72, we intend to archive this repository and are thus triaging and resolving all open issues)
This issue didn't get any traction 5 years ago and seems safe to close. I would suggest that this is less of a standards question but rather something that individual browsers should experiment with, so if there's still interest it may make sense to file bugs with browsers.
Sometimes 60fps is unreasonable for a given page and device, so perhaps we shouldn't always strive to achieve that. Also, 60fps during page load (with heavy style recalc, layout, JS execution, etc.) is usually unreasonable even for more powerful devices.
Perhaps we should always load pages at 30fps, and then switch into 60fps once we've detected that it's taking less than 16.6ms of CPU time to generate each frame.
The text was updated successfully, but these errors were encountered: