TestUFO Doesn't Work at 120fps on 120 Hz Apple iDevices
Posted: 18 Jan 2020, 18:06
TestUFO Doesn't Work at 120fps on the 120 Hz iPads
This becomes more urgent as 120Hz gets mainstreamed (with the boom of 120 Hz smartphones)
We currently have a lone-standout problem:
Works -- All current versions of all desktop browsers
Works -- Razer 120 Hz phones
Works -- Pixel 90 Hz phones
Works -- OnePlus 90 Hz phones
Works -- Xiaomi 144 Hz phones
Works -- Samsung 120 Hz Galaxy (Google Analytics shows Samsung useragents green at 120Hz!)
DOES NOT WORK -- Apple 120 Hz iPad
Possible Issue With Web Standards (W3C / WHATWG)
I've submitted a modification to a HTML standard (HTML 5.2 Section 7.1.4.2) that was accepted by W3C. However, Apple still hasn't fallen in line with this.This may be a combination of a web standards issue and a political issue.
Here's the GitHub issue I created at WHATWG:
Steps On Standardizing Refresh Rate Behaviours With Web Browsers (120 Hz, 144 Hz, 240 Hz...)
This lone-standout issue becomes more urgent due to mainstream 120 Hz phone launches this year. The 120 Hz iPhone/Galaxy phones is undoubted going to be far more popular than the 120 Hz iPad. It's a big step towards mainstreaming of 120 Hz.
If you're a person well-versed in technical issues or as a software developer -- feel free to add your comment/discussion. Even if you aren't a participant in standards, you are welcome to at least "Like" the posts I made at GitHub.
This becomes more urgent as 120Hz gets mainstreamed (with the boom of 120 Hz smartphones)
We currently have a lone-standout problem:
Works -- All current versions of all desktop browsers
Works -- Razer 120 Hz phones
Works -- Pixel 90 Hz phones
Works -- OnePlus 90 Hz phones
Works -- Xiaomi 144 Hz phones
Works -- Samsung 120 Hz Galaxy (Google Analytics shows Samsung useragents green at 120Hz!)
DOES NOT WORK -- Apple 120 Hz iPad
Possible Issue With Web Standards (W3C / WHATWG)
I've submitted a modification to a HTML standard (HTML 5.2 Section 7.1.4.2) that was accepted by W3C. However, Apple still hasn't fallen in line with this.This may be a combination of a web standards issue and a political issue.
Here's the GitHub issue I created at WHATWG:
Steps On Standardizing Refresh Rate Behaviours With Web Browsers (120 Hz, 144 Hz, 240 Hz...)
This lone-standout issue becomes more urgent due to mainstream 120 Hz phone launches this year. The 120 Hz iPhone/Galaxy phones is undoubted going to be far more popular than the 120 Hz iPad. It's a big step towards mainstreaming of 120 Hz.
If you're a person well-versed in technical issues or as a software developer -- feel free to add your comment/discussion. Even if you aren't a participant in standards, you are welcome to at least "Like" the posts I made at GitHub.