commit | 2a3f733d9826d3868299f98bd17d91d4bfcb4bb4 | [log] [tgz] |
---|---|---|
author | Maksim Sisov <msisov@igalia.com> | Tue Mar 21 22:42:40 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 21 22:42:40 2023 |
tree | 62d8229bad2a751266eb6082a2b4ee4a2d71112d | |
parent | 5ba871f818a96420e847c38e3f7e7ac78641edaf [diff] |
[ios] support high refresh rate displays. To support high refresh rate (>60), this CL does the following fixes: 1) Added GetMaximumRefreshFrameInterval() to ExternalBeginFrameSource, which is used to determine a maximum supported refresh rate that RootCompositorFrameSinkImpl uses when preferred refresh rate is undecided. Previously, it used BeginFrameArgs::DefaultInterval(), which defaults to 60FPS. 2) BFS iOS fetches the maximum supported refresh rate via UIScreen and uses that value as a default setting and as a reference value so that the preferred refresh rate doesn't exceed that value, which is an exception. For phones, CADisableMinimumFrameDurationOnPhone has to be set. Otherwise, the maximum refresh rate will be caped at 60FPS. See https://developer.apple.com/documentation/quartzcore/optimizing_promotion_refresh_rates_for_iphone_13_pro_and_ipad_pro?language=objc Cq-Include-Trybots: luci.chromium.try:ios-blink-dbg-fyi Bug: 1413559 Change-Id: Ia1fdc0c0703dd88cd10d74c3b1df6a8e178b6f21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4350308 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/main@{#1120242}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.