[WebXR] Fix closure compiler mangling XRSession.enabledFeatures
#93593
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.
Currently, when running a WebXR app with a release build using the Closure compiler, it'll crash on entering an XR session with this error (from Chrome with the WebXR API Emulator):
This was introduced by PR #88411, which added a reference to
XRSession.enabledFeatures
(among other things), but I forgot to add it to thewebxr.extern.js
file for the Closure compiler, in order to prevent it from doing its usual name mangling thing.