cc: Always use SetNeedsBeginFrame to request the next BeginFrame
commitb04b301af83033df836efd65c4f0f6be72dce0c3
authorbrianderson@chromium.org <brianderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 14 Sep 2013 05:04:45 +0000 (14 05:04 +0000)
committerbrianderson@chromium.org <brianderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 14 Sep 2013 05:04:45 +0000 (14 05:04 +0000)
tree907eb8c5ae9957f36aed5f912f0ea3ac540c5ef8
parent01aba0df5ec1dcdb17455675e5e7cad1c9561ab5
cc: Always use SetNeedsBeginFrame to request the next BeginFrame

This avoids relying on SwapBuffers to implicitly trigger the next
BeginFrame. Only a single code path is used to request the next
BeginFrame now: SetNeedsBeginFrame(true).

This avoids issues where OutputSurface subclasses might not call
OutputSurface::DidSwap() when they need to or when we early out
a swap request and don't actually swap anything.

BUG=289755

Review URL: https://chromiumcodereview.appspot.com/23498035

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223218 0039d316-1c4b-4281-b951-d872f2087c98
cc/output/output_surface.cc
cc/output/output_surface.h
cc/output/output_surface_unittest.cc
cc/scheduler/scheduler.cc
cc/scheduler/scheduler.h
cc/scheduler/scheduler_state_machine.cc
cc/scheduler/scheduler_unittest.cc