-
kylechar authored
With OOP-D enabled Compositor::SetDisplayVSyncParameters() won't necessarily be called anymore as most of that logic moves to the GPU process. This means that |refresh_rate_| won't be updated ever and would be incorrect. The vsync interval in received BeginFrameArgs is equivalent to the refresh rate, so plumb that information out of cc::Scheduler and back into ui::Compositor. This should always work correctly. This CL also removes ContextFactory::GetRefreshRate(). This set the initial value for |refresh_rate_| in tests. This no longer serves any purpose, as |refresh_rate_| is only used for metric reporting that doesn't impact tests. Tests that want to run faster already setup a BeginFrameSource with the appropriate shorter interval. Bug: 899300 Change-Id: I8f7dcbb984a4cd804712d39a571e43ad627c9d4b Reviewed-on: https://chromium-review.googlesource.com/c/1311077Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#604783}
d96169b4