Set stencilBuffer property of WebGLRenderTarget in WebXRManager #24488
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.
Description
In case a browser doesn't implement the WebXR Layers API, the
WebXRManager
doesn't set thestencilBuffer
property on the render target. The underlying framebuffer, however, can have a stencil buffer. Functionally the stencil buffer seems to work for as far as I could test, but the render target incorrectly reports that it doesn't have one.This PR simply ensures the
stencilBuffer
property is set accordingly. This is in line with the way it's done in the code path for browsers that do implement the WebXR Layers API (line 325).