iPad Pro 120hz online test


tps3443

macrumors 65816
Jan 24, 2019
1,290
821
NC,USA
To this day that website does not work properly and still reports 120Hz. I tried chrome, and Safari.
 

Blur Busters

macrumors newbie
Founder of TestUFO here.

Unfortunately, this is not TestUFO's fault.

Apple is currently in violation of compliance of the HTML 5.2 and HTML 5.3 specification, section 7.1.4.2. Since Apple forces Chrome to use the Safari engine, the restriction also applies to all web browsers installed on the 120 Hz iPads.

Currently, FireFox, Chrome, Opera, and Edge (74+) are all compliant and even works at 240 Hz

HTML 5.3, Section 7.1.4.2, Processing Model

If there is a top-level browsing context B that the user agent believes would not benefit from having its rendering updated at this time, then remove from docs all Document objects whose browsing context’s top-level browsing context is B.

NOTE There are many factors that affect the ideal update frequency for the top-level browsing context including performance, power, background operation, quality of user experience, refresh rate of display(s), etc. When in foreground and not constrained by resources (i.e. performance, battery versus mains power, other resource limits), the user agent normally prioritizes for maximum quality of user experience for that set of Documents by matching update frequency and animation frame callback rate to the current refresh rate of the current display (usually 60Hz, but refresh rate may be higher or lower). When accommodating constraints on resources, the update frequency might automatically run at a lower rate. Also, if a top-level browsing context is in the background, the user agent might decide to drop that page to a much slower 4Hz, or even less.

NOTE Another example of why a browser might skip updating the rendering is to ensure certain tasks are executed immediately after each other, with only microtask checkpoints interleaved (and without, e.g., animation frame callbacks interleaved). For example, a user agent might wish to coalesce callbacks together, with no intermediate rendering updates. However, when are no constraints on resources, there must not be an arbitrary permanent user agent limit on the update rate and animation frame callback rate (i.e., high refresh rate displays and/or low latency applications).
Until Apple fixes this, at least for plugged-in 120 Hz iPads, it is just not possible to run TestUFO at above 60 frames per second on Apple iPads.
 
Last edited:

TheRealAlex

macrumors 68000
Sep 2, 2015
1,902
1,049
Founder of TestUFO here.

Unfortunately, this is not TestUFO's fault.

Apple is currently in violation of compliance of the HTML 5.2 and HTML 5.3 specification, section 7.1.4.2. Since Apple forces Chrome to use the Safari engine, the restriction also applies to all web browsers installed on the 120 Hz iPads.

Currently, FireFox, Chrome, Opera, and Edge (74+) are all compliant and even works at 240 Hz



Until Apple fixes this, at least for plugged-in 120 Hz iPads, it is just not possible to run TestUFO at above 60 frames per second on Apple iPads.
And Apple will never fix or address this since running the browser at 120 Hz would Incur penalty on battery life.
 

tps3443

macrumors 65816
Jan 24, 2019
1,290
821
NC,USA
Repeating:

Until Apple fixes this, at least for plugged-in 120 Hz iPads, it is just not possible to run TestUFO at above 60 frames per second on Apple iPads.
Wow! Nice to see the founder of blur busters reply him self on here. I’ve been using that website for years. I’ve been through to many G-sync monitors, overclocking the refresh rate, and using the ufo test.
 

TheRealAlex

macrumors 68000
Sep 2, 2015
1,902
1,049
Founder of TestUFO here.

Unfortunately, this is not TestUFO's fault.

Apple is currently in violation of compliance of the HTML 5.2 and HTML 5.3 specification, section 7.1.4.2. Since Apple forces Chrome to use the Safari engine, the restriction also applies to all web browsers installed on the 120 Hz iPads.

Currently, FireFox, Chrome, Opera, and Edge (74+) are all compliant and even works at 240 Hz



Until Apple fixes this, at least for plugged-in 120 Hz iPads, it is just not possible to run TestUFO at above 60 frames per second on Apple iPads.
Let’s ask a serious question, obviously you are well versed in this subject. Questions is Why doesn’t Apple fix this and have you been given a reason by Apple ?
Why do you think Apple doesn’t fix this ?