feat(xr): backend-aware WebXR support detection (isDeviceSupported)#8948
Merged
Conversation
Build size reportThis PR changes the size of the minified bundles.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a way to detect whether a WebXR session can run on a given graphics backend, and makes the existing reactive XR availability backend-aware. This is needed because WebGPU WebXR is supported only on a subset of platforms, whereas WebGL WebXR has wider support — so the same headset can support a session under WebGL but not under WebGPU.
Changes:
XrManager.isDeviceSupported(deviceType, type)reporting whether an immersive session of the given type can run on a given graphics backend. It can be called before a graphics device is created, so an app can decide which backend to request for XR.XrManager#isAvailableand theavailable/available:[type]events) now accounts for the active graphics backend. Previously it reflected only what the browser/headset reported regardless of backend, so on a WebGPU device a session could be reported available when it could not actually start. WebGL behavior is unchanged.API Changes:
XrManager.isDeviceSupported(deviceType: string, type: string): Promise<boolean>(static).XrManager#isAvailable(type)and theavailable/available:[type]events are now backend-aware. WebGL results are identical; WebGPU results are now accurate — a session is reported available only if it can actually run on the current device.