You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an incremental change to the WebXR API to add optional support for dynamic viewport scaling. This is intended to let applications render to a subset of the full viewport and adjust that scale on a per-frame basis if needed to reach target framerates.
This was discussed in immersive-web/webxr#1091 and multiple calls with the immersive-web group. The changes were merged into the main specification via immersive-web/webxr#1132 , but to the best of my knowledge this hasn't been launched in any other browser yet.
As per discussion on the Chrome intent-to-ship thread, I'm looking for feedback on the change.
For context, the goal is that this API is optional for UAs. It would be a valid implementation to provide a requestViewportScale method that does nothing. If it is supported, the UA can optionally provide a recommendedViewportScale numeric attribute based on internal heuristics, but it's also valid to keep that undefined.
The text was updated successfully, but these errors were encountered:
Request for Mozilla Position on an Emerging Web Specification
Explainer: https://github.com/immersive-web/webxr/blob/master/explainer.md#dynamic-viewport-scaling
Other information
This is an incremental change to the WebXR API to add optional support for dynamic viewport scaling. This is intended to let applications render to a subset of the full viewport and adjust that scale on a per-frame basis if needed to reach target framerates.
This was discussed in immersive-web/webxr#1091 and multiple calls with the immersive-web group. The changes were merged into the main specification via immersive-web/webxr#1132 , but to the best of my knowledge this hasn't been launched in any other browser yet.
As per discussion on the Chrome intent-to-ship thread, I'm looking for feedback on the change.
I've requested TAG review here: w3ctag/design-reviews#588
For context, the goal is that this API is optional for UAs. It would be a valid implementation to provide a
requestViewportScale
method that does nothing. If it is supported, the UA can optionally provide arecommendedViewportScale
numeric attribute based on internal heuristics, but it's also valid to keep that undefined.The text was updated successfully, but these errors were encountered: