Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

tps3443

macrumors 65816
Jan 24, 2019
1,404
905
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 68030
Sep 2, 2015
2,659
1,737
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.
 
  • Like
Reactions: DanTSX

tps3443

macrumors 65816
Jan 24, 2019
1,404
905
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 68030
Sep 2, 2015
2,659
1,737
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 ?
 

Ninja Dom

macrumors 6502a
Feb 12, 2007
635
131
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 ?
Old thread, I know.

Apple has the ability to fix this because Safari runs at high refresh rates on a Mac. The testufo site works fine at 120Hz on a Mac plugged into a High Refresh Rate monitor.
 

Natzoo

macrumors 68000
Sep 16, 2014
1,982
615
Old thread, I know.

Apple has the ability to fix this because Safari runs at high refresh rates on a Mac. The testufo site works fine at 120Hz on a Mac plugged into a High Refresh Rate monitor.
I tried these tests recently on my iPad and it still claims 60hz, does that mean safari cannot run at 120hz, or is it the adaptive refresh noticing it's a test?
 
  • Like
Reactions: Darajavahus

Digitalguy

macrumors 68020
Apr 15, 2019
2,398
2,172
Yes, it's because of variable refresh rate. On both my 10.5 and 11 it stays at 60 even if I try to scroll in split screen on something else at the same time...
On my Tab S7+ it's 120hz. The smaller Tab S7 has the same "issue" since it has variable refresh rate like the iPad (because, like the iPad, it's a LCD, not OLED). Variable refresh rate on Oled is for now only limited to the Note20 ultra as far as I know. Apple couldn't get enough for the iPhone pro and even Samsung didn't make it for the S7+.
For fun I tried on my gaming monitors, they report their max rates, 144 and 240. However, only if they run as the main display. When I run from a laptop as an extended display it shows 60, even it windows is reporting 240 in the external display. Once I move to the external display only, it goes back to max.
 

Ninja Dom

macrumors 6502a
Feb 12, 2007
635
131
Yes, it's because of variable refresh rate. On both my 10.5 and 11 it stays at 60 even if I try to scroll in split screen on something else at the same time...
On my Tab S7+ it's 120hz. The smaller Tab S7 has the same "issue" since it has variable refresh rate like the iPad (because, like the iPad, it's a LCD, not OLED). Variable refresh rate on Oled is for now only limited to the Note20 ultra as far as I know. Apple couldn't get enough for the iPhone pro and even Samsung didn't make it for the S7+.
For fun I tried on my gaming monitors, they report their max rates, 144 and 240. However, only if they run as the main display. When I run from a laptop as an extended display it shows 60, even it windows is reporting 240 in the external display. Once I move to the external display only, it goes back to max.
Okay so on the iPad Pro, will you actually get 120fps in Safari even though the benchmark website reports 60Hz??
 

Blur Busters

macrumors newbie
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 ?
Battery efficiency for things like animated banner ads. A legitimate reason.

Technically, they could just use a permissions-based prompt, like for microphone requesrs, “This web page requests 120fps animations which may consume more battery power. Allow / Cancel?”

From some statements by Webkit member @smfr on Twitter, they also think that the HTML requestAnimationFrame() API is a poor method for 120fps, but it has some major advantages for scientific-precision animations that are self-detecting.

Are there anybody here who works with iOS apps on 120 Hz iPads? I’m considering getting back into iOS development to solve this problem with a custom browser app (off Safari HTML5 view, like Chrome or FireFox for iPad)

Opting-in via plist and build a browser wrapper in xcode with this setting:
<key>CADisableMinimumFrameDuration</key> <true/>

Then testing a site such as vsynctester website (or the testufo link above) in the app-specific browser view, and seeing if it detects 120 Hz.

Some Apple developer docs on enabling 120Hz in specific apps:
 
Last edited:

Ninja Dom

macrumors 6502a
Feb 12, 2007
635
131
Mac users.

Be aware everyone, as of macOS 11.6 www.testufo.comreports that Safari browser runs at 60fps maximum. Chrome browser still runs at 120fps but not Safari.

I’m not sure if this is actually something within Safari or if testufo is reporting the wrong information.
 
  • Like
Reactions: ElectronGuru

Sheepish-Lord

macrumors 6502a
Oct 13, 2021
643
1,128
If you look @Blur Busters statement it says TestUFO can't be run at 120. Says nothing about ProMotion not working at all within Safari just their test doesn't detect it.

We've had ProMotion for years on iPads and I would think someone would have made a bigger deal if it didn't work.
 

Ninja Dom

macrumors 6502a
Feb 12, 2007
635
131
If you look @Blur Busters statement it says TestUFO can't be run at 120. Says nothing about ProMotion not working at all within Safari just their test doesn't detect it.

We've had ProMotion for years on iPads and I would think someone would have made a bigger deal if it didn't work.
Oh yeah, we know. It’s just that it used to be detected on Macs at 120Hz running Safari in Big Sur. Something has changed and it isn’t detected on Macs either now.
 
  • Like
Reactions: Sheepish-Lord
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.