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

[bugzilla-daemon at webkit.org]

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

--- Comment #61 from mdrejhon <mark at blurbusters.com> ---
(In reply to Jeffrey Blanz from comment #60)
> I would actually have to say the opposite. This should be marked resolved
> because of the following: 

Let's wait until the upstream pushes and a royal flush occurs.

> 1. I just tested my M1 Pro MacBook Pro, with the lid open, with safari 17.5
> and a 165hz monitor. My Mac got 120hz while the external monitor got 165hz.

Then if TestUFO running on secondary shows 165Hz, they have fixed the problem.  

Good, I'll update my OS to the latest MacOS.  I'm one version behind.

> 2. iPhone Pros will be getting 120hz fixed in 278949 at main (596b3b01497f):
> <https://commits.webkit.org/278949@main>

Good, but it's not upstream yet.

> 3. The M4 iPad Pros will also be fixed with 278949 at main (596b3b01497f):
> <https://commits.webkit.org/278949@main>

Good, but it's not upstream yet.

> This means that there are no longer any scenarios where native
> requestanimationframe is not supported, as soon as 278949 at main is pushed to
> the public. Besides when the feature flag "prefer page rendering updates
> near 60fps" is enabled. That is a different issue though.

Fair.  Once all checkboxes go green, I'll declare it closed.

Until the issue makes it to production firmwares and devices, let's keep this open, shall we?  :-)

Good news indeed, though.

-- 
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/20240519/c1dc079b/attachment-0001.htm>