cc: Always use SetNeedsBeginFrame to request the next BeginFrame

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
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=223218

[brianderson, 2013-09-13 20:19:10]

This was a pretty straight forward rebase. I've added a comment to the only part
of the patch that is different than the version enne approved in
https://codereview.chromium.org/23892022.

https://codereview.chromium.org/23498035/diff/1/cc/scheduler/scheduler_unitte...
File cc/scheduler/scheduler_unittest.cc (right):

https://codereview.chromium.org/23498035/diff/1/cc/scheduler/scheduler_unitte...
cc/scheduler/scheduler_unittest.cc:807: // We need a BeginFrame where we don't
swap to go idle.
Had to add this to @epenner's test to make sure we go idle.

[enne (OOO), 2013-09-13 20:58:57]

Still lgtm.

[commit-bot: I haz the power, 2013-09-14 00:10:23]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/brianderson@chromium.org/23498035/1

[commit-bot: I haz the power, 2013-09-14 05:04:52]

Change committed as 223218