Steps to reproduce
Get a display that supports 120Hz refresh rates.
Observe that the FPS counter rendered on the page says “FPS: 60”
For comparison, visiting the same page in current stable Chrome 36 does render the page at 120 fps.
Expected: The requestAnimationFrames should be running at 120 fps.
Dev Channel specific:
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Kamen M.”
Changed Assigned To to “Christian F.”
Changed Steps to Reproduce
Changed Assigned To to “Rico M.”
Changed Status to “Confirmed”
Changed Status from “Confirmed” to “Won’t fix”
This is NOT “By Design”
This is a VIOLATION of W3C Animation Timing specification to synchronize requestAnimationFrame() to refresh rate – see end of section 5 of https://www.w3.org/TR/animation-timing/
Chrome, Safari, FireFox, all do animations at 50Hz, 75Hz, 85Hz, 100Hz, 120Hz flawlessly. IE and Edge are the only browsers that fail.
Related, with much more complaints and reproduction:
Lots of people were complaining!
Some versions of IE11 on some systems now do 120Hz properly on certain displays with certain display drivers (but not as reliably as the other browsers). The Edge browser completely FAILS on this on 100% of systems.
100% of your competition is 100% COMPLIANT.
Why is this a “Wont Fix” ???
Unrelated, another topic, but related to standardization of refresh rates: Oculus and VIVE virtual reality goggles, they all run at 90Hz, and some of them are about to develop W3C-compliant VR extensions, and ability to synchronize to other than 60Hz is exceedingly critical in this use-case.
This is now illegal in HTML 5.2
Section 188.8.131.52 of HTML 5.2, explicitly (with an “MUST NOT”) mandates there should be absolutely no permanent frame rate caps.