diff options
| author | bors-servo <lbergstrom+bors@mozilla.com> | 2019-10-16 20:02:10 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-16 20:02:10 -0400 |
| commit | 14240bee81bc8b5c5a55d1ed5d5719cf8ee342ee (patch) | |
| tree | 178dbb4318905a147be322c3563638c11d1c1372 /components/script/dom/bindings/codegen | |
| parent | 9032207b8a0f5d7328613e16f89e7c128ed5cb8b (diff) | |
| parent | 24bfca9b71642dfc1e5b9371c352b5efaf6f0802 (diff) | |
| download | servo-14240bee81bc8b5c5a55d1ed5d5719cf8ee342ee.tar.gz servo-14240bee81bc8b5c5a55d1ed5d5719cf8ee342ee.zip | |
Auto merge of #24452 - Manishearth:raf-lifecycle, r=asajeffrey
Always request new XR frames
Currently we only request XR frames when there is a rAF callback queued up.
This is incorrect, see https://immersive-web.github.io/webxr/#xr-animation-frame
With this change we always request updated frame state regardless of whether or not the user has queued up callbacks.
In addition to being spec-correct, this means that we can reliably listen for events in the OpenXR backend in the rAF loop itself, instead of having to set up a second spinning loop for when the rAF is inactive. This lets us implement visibility states for openxr without having to worry about the user never receiving the wakeup call because the rAF loop isn't pumping.
See also: https://github.com/immersive-web/webxr/issues/877
r? @asajeffrey
Diffstat (limited to 'components/script/dom/bindings/codegen')
0 files changed, 0 insertions, 0 deletions