Move outputContext from XRSession to XRRenderState #15507
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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}