Intent to Prototype & Ship: WebXR enabledFeatures attribute
Alex Cooper
Contact emails
alco...@chromium.orgExplainer
NoneSpecification
https://immersive-web.github.io/webxr/#dom-xrsession-enabledfeaturesSummary
Applications can query for which features from their supplied XRSessionInit were actually enabled on a newly created XRSession (note that this will really only be useful for optionalFeatures, since a session that cannot serve all requiredFeatures would be rejected). Most features have some way for developers to detect if they were granted; however, for some features the signal of whether or not a feature was enabled may tie closely with data for a feature just not being available "right now", rather than data not being available "ever". By querying enabledFeatures, a developer can determine if any helpful hints (e.g. to improve/start tracking) should be shown, or if a feature will never be supported in the current session. It is also possible that future WebXR features may not have other signals to detect whether or not they were enabled.
Blink component
Blink>WebXRTAG review
https://github.com/w3ctag/design-reviews/issues/782TAG review status
Issues addressedRisks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Debuggability
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
YesIs this feature fully tested by web-platform-tests?
YesFlag name
Requires code in //chrome?
FalseTracking bug
https://crbug.com/1377430Launch bug
https://launch.corp.google.com/launch/4225596Estimated milestones
No milestones specified
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5082665189900288
Yoav Weiss
Specification
https://immersive-web.github.io/webxr/#dom-xrsession-enabledfeaturesSummary
Applications can query for which features from their supplied XRSessionInit were actually enabled on a newly created XRSession (note that this will really only be useful for optionalFeatures, since a session that cannot serve all requiredFeatures would be rejected). Most features have some way for developers to detect if they were granted; however, for some features the signal of whether or not a feature was enabled may tie closely with data for a feature just not being available "right now", rather than data not being available "ever". By querying enabledFeatures, a developer can determine if any helpful hints (e.g. to improve/start tracking) should be shown, or if a feature will never be supported in the current session. It is also possible that future WebXR features may not have other signals to detect whether or not they were enabled.
Blink component
Blink>WebXRTAG review
https://github.com/w3ctag/design-reviews/issues/782TAG review status
Issues addressedRisks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Debuggability
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
YesIs this feature fully tested by web-platform-tests?
Yes
Flag name
Requires code in //chrome?
FalseTracking bug
https://crbug.com/1377430Launch bug
https://launch.corp.google.com/launch/4225596Estimated milestones
No milestones specified
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5082665189900288This intent message was generated by Chrome Platform Status.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz056atoRuWVtMncotiDixvRM2TQKDicCreLJqK3v8rcnA%40mail.gmail.com.
slightlyoff via Chromestatus
Alex Cooper
Alex Cooper
Rick Byers
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz2M9qNsN1OQn1i%2Bf3ytCwX4%3DR-nR%3DiJ%2Be6KvgUSR9VEcA%40mail.gmail.com.
Mike Taylor
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY90kFMJ%2Bb1Zuo2U31w7RoroEwwJGe_FCjj78fxyATuf6A%40mail.gmail.com.