Trigger didCommitAndDrawCompositorFrame on Swapbuffers complete

Trigger didCommitAndDrawCompositorFrame on fullscreen Swapbuffers

The compositor isn't really running in this case, so we have to run the callback here to make sure the next frame is created.

BUG=
TEST=


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=112417

[piman, 2011-12-01 01:13:10]

Why not do it in SwapBuffers()? The "compositor" rate limit will still kick in,
and if it works in windowed mode, it should work in fullscreen mode too, right?

[jbauman, 2011-12-01 04:59:08]

On 2011/12/01 01:13:10, piman wrote:
> Why not do it in SwapBuffers()? The "compositor" rate limit will still kick
in,
> and if it works in windowed mode, it should work in fullscreen mode too,
right?

Ok, changed to do that.

[piman, 2011-12-01 05:04:05]

lgtm

http://codereview.chromium.org/8760018/diff/3001/content/renderer/render_widg...
File content/renderer/render_widget_fullscreen_pepper.cc (right):

http://codereview.chromium.org/8760018/diff/3001/content/renderer/render_widg...
content/renderer/render_widget_fullscreen_pepper.cc:492: if
(is_accelerated_compositing_active_)
No need for the if. It should be always true when we get here.

[commit-bot: I haz the power, 2011-12-01 05:14:35]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jbauman@chromium.org/8760018/6001

[commit-bot: I haz the power, 2011-12-01 06:51:43]

Change committed as 112417