Closed Bug 1531929 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 15507 - Move outputContext from XRSession to XRRenderState

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox68 fixed)

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 15507 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/15507
Details from upstream follow.

Brandon Jones <bajones@chromium.org> wrote:

Move outputContext from XRSession to XRRenderState

This requires all sessions that were previously setting an
outputContext in the requestSession call to move that assignment to an
updateRenderState call post-session-creation instead. Additionally,
"inline" sessions can now be created without an outputContext but must
still have one assigned to them before any requestAnimationFrame
callbacks will be processed.

Bug: 928417
Change-Id: I469fab8c3f641870387f2f92aee52182016efe37
Reviewed-on: https://chromium-review.googlesource.com/c/1476097
Commit-Queue: Brandon Jones \<bajones@chromium.org>
Reviewed-by: Brian Sheedy \<bsheedy@chromium.org>
Reviewed-by: Klaus Weidner \<klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636557}

Ran 21 tests and 29 subtests
OK     : 21
PASS   : 2
FAIL   : 27

New tests that have failures or other problems:
/webxr/xrSession_transfer_outputContext.https.html
    Ensure that XRPresentationContexts are properly transfered between session: FAIL
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0100e2fbd52f
[wpt PR 15507] - Move outputContext from XRSession to XRRenderState, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/bd36f87ea43f
[wpt PR 15507] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.