Use vsync manager regardless of begin frame settings
There was some hope that the ui::CompositorVSyncManager could be removed once --enable-begin-frame-scheduling was turned on. Unfortunately, the vsync manager is used by two additional systems that can't be easily removed: DelegatedFrameHost::AttemptFrameSubscriberCapture as well as components/exo/wayland/server.cc. The latter may go away eventually. If so, then the frame capture could then be changed to more simple polling as needed instead of vsync manager and observer system that needs to be plumbed everywhere. In the medium term, the vsync manager needs to live on in all paths. This means that BrowserCompositorOutputSurface and ui::Compositor always need to update the vsync manager with changes. Conditionals for whether or not to send vsync information to renderers just get moved down the pipeline from the output surface to DelegatedFrameHost. Review-Url: https://codereview.chromium.org/2277883002 Cr-Commit-Position: refs/heads/master@{#414186}
Showing
Please register or sign in to comment