Mac: Fix bad framerate when capturing tab

Mac: Fix bad framerate when capturing tab

The fix for this issue, namely, that we must draw contents manually and
immediately when a window is occluded because Cocoa will not draw them
for us, was not ported to the browser compositor.

Plumb this explicitly through a ShouldAckImmediately callback for
CompositingIOSurfaceLayerClient and BrowserCompositorViewMacClient.

Also check for vsync disabling in the ShouldAckImmediately instead of
running it (unnecessarily) through CompositingIOSurfaceContextMac.

BUG=393390, 350410
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=284856

[ccameron, 2014-07-22 02:20:37]

Sorry this took so long to get to!

[miu, 2014-07-22 20:07:47]

lgtm, thanks!  :)

[ccameron, 2014-07-22 20:25:54]

Thanks!

[ccameron, 2014-07-22 20:25:59]

The CQ bit was checked by ccameron@chromium.org

[commit-bot: I haz the power, 2014-07-22 20:28:08]

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

[commit-bot: I haz the power, 2014-07-22 23:51:09]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu_triggered...)

[commit-bot: I haz the power, 2014-07-23 01:42:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-23 01:42:52]

Try jobs failed on following builders:
  win_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu_triggered...)

[ccameron, 2014-07-23 01:43:39]

The CQ bit was checked by ccameron@chromium.org

[commit-bot: I haz the power, 2014-07-23 01:44:36]

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

[commit-bot: I haz the power, 2014-07-23 06:18:13]

Change committed as 284856