WebVR: handle window.rAF while presenting

WebVR: handle window.rAF while presenting

We currently aren't processing the normal vsync/BeginFrame events
during WebVR presentation, this means that only vrDisplay.rAF
callbacks get executed, not window.rAF callbacks. This breaks
applications that depend on window.rAF for background processing,
so we should continue executing those callbacks too.

This patch does not enable requestIdleCallback handling, that is
significantly more complex and we're looking into that separately.

BUG=704341
Review-Url: https://codereview.chromium.org/2812253004
Cr-Commit-Position: refs/heads/master@{#464233}
Committed: https://chromium.googlesource.com/chromium/src/+/5873ff63b705173921eddc8741704fbde962a41f

[klausw, 2017-04-12 22:40:01]

klausw@chromium.org changed reviewers:
+ bajones@chromium.org

[bajones, 2017-04-12 22:52:26]

LGTM with one question: Will this fire even if no VRDisplay.rAF's have been
scheduled? I _think_ that's the cause of a race condition I'm seeing.

[klausw, 2017-04-12 23:43:04]

On 2017/04/12 22:52:26, bajones wrote:
> LGTM with one question: Will this fire even if no VRDisplay.rAF's have been
> scheduled? I _think_ that's the cause of a race condition I'm seeing.

I don't think so, but that sounds like a separate pre-existing condition.

[klausw, 2017-04-12 23:43:10]

The CQ bit was checked by klausw@chromium.org

[commit-bot: I haz the power, 2017-04-12 23:43:44]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-13 01:39:11]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492040590379970, "parent_rev":
"7cd3f1eb560d6d2478fd9caf0ae6e993ecb8d305", "commit_rev":
"5873ff63b705173921eddc8741704fbde962a41f"}

[commit-bot: I haz the power, 2017-04-13 01:40:01]

Description was changed from

==========
WebVR: handle window.rAF while presenting

We currently aren't processing the normal vsync/BeginFrame events
during WebVR presentation, this means that only vrDisplay.rAF
callbacks get executed, not window.rAF callbacks. This breaks
applications that depend on window.rAF for background processing,
so we should continue executing those callbacks too.

This patch does not enable requestIdleCallback handling, that is
significantly more complex and we're looking into that separately.

BUG=704341
==========

to

==========
WebVR: handle window.rAF while presenting

We currently aren't processing the normal vsync/BeginFrame events
during WebVR presentation, this means that only vrDisplay.rAF
callbacks get executed, not window.rAF callbacks. This breaks
applications that depend on window.rAF for background processing,
so we should continue executing those callbacks too.

This patch does not enable requestIdleCallback handling, that is
significantly more complex and we're looking into that separately.

BUG=704341

Review-Url: https://codereview.chromium.org/2812253004
Cr-Commit-Position: refs/heads/master@{#464233}
Committed:
https://chromium.googlesource.com/chromium/src/+/5873ff63b705173921eddc874170...
==========

[commit-bot: I haz the power, 2017-04-13 01:40:02]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/5873ff63b705173921eddc874170...