[Webkit-unassigned] [Bug 173434] Support for 120Hz requestAnimationFrame

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=173434

--- Comment #6 from mdrejhon <mark at blurbusters.com> ---
New article:
Competing mobile phone manufacturers are using TestUFO to show off 120 Hz and 144 Hz:
https://www.lowyat.net/2020/203823/xiaomi-releases-demo-video-of-redmi-k30-5g-display-running-with-144hz-refresh-rate/

You see the YouTube video.  Apparently, they modified generic Webkit to be 144fps compatible, so ignore the "UNSUPPORTED" message (it will be remedied in a future version of TestUFO update)

It would be in Apple's business interests to make sure that 120 Hz iPhone (when it comes out later this year), supports 120fps requestAnimationFrame() minimally.  It is not mutually exclusive with complying with the WHATWG specification.

Power consumption is also indeed a legitimate worry but this can be solved by giving the user the choice of Performance versus Efficiency.

Google "Blur Busters" in the news lately.  As an entity in the Refresh Rate Race to future Retina Refresh Rates, we're square and center in many of these standardization initiatives.

Minimal fps=Hz sync support is easy to do, and (now with Microsoft falling in line) is quite defacto standardized in all web browsers by all vendors on all desktops, tablets, and mobiles -- with the sole exception of Apple.  We should probably join WHATWG to send this memo.

I have lots of Apple devices (own 4 iPads) and being in the Apple ecosysystem too, it is a bit concerning that Apple has been a laggard in the refresh rate race.  The spatial retina resolution cow was milked, and now the pressure is on commoditizing retina refresh rates, so it is no longer a fad.   4K was insanely expensive 20 years ago, and now 4K is a Walmart sale.  High-Hz will be pervasive as it is another area of progress that has freed up thanks to technology.   Browsers need to keep up, and Apple should too.  Politics on power vs performance can be solved by a simple setting.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200114/26d4c78a/attachment.htm>