Intent to Prototype: WebXR Spec Parity

[Alex Cooper]

Note: This Feature is intended to replace https://chromestatus.com/feature/5157293366181888 and https://chromestatus.com/feature/5984008124497920

Contact emails
alco...@chromium.org, baj...@chromium.org, bia...@chromium.org

Explainer
None

Specification
https://immersive-web.github.io/webxr

Summary
Updates our implementation of the WebXR specification to provide a few attributes that have been added over time. These are generally attributes that developers find useful or enable small performance improvements. These include but are not limited to: Setting/Querying the framerate on an XRSession (including supported framerates), Angular/Linear Velocities, Predicted Display Time of a Frame, isSystemKeyboardSupported, and XRWebGLLayer fixedFoveation


Blink component
Blink>WebXR

Motivation
None


Initial public proposal
N/a

TAG review
https://github.com/w3ctag/design-reviews/issues/545

TAG review status
Issues addressed

Risks


Interoperability and Compatibility
None


Gecko: Positive (https://github.com/mozilla/standards-positions/issues/218)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/155) Safari has announced WebXR support for the Vision Pro, even if they have not replied to the standards-position request as yet.

Web developers: Positive https://groups.google.com/a/chromium.org/g/blink-dev/c/0Bctfvd-Sg8/m/e9Mq_TrJBgAJ https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz36QHGLYyz2H_6CnsuiwN_y002YRg%2BCeWzs_dvPxhLEWg%40mail.gmail.com

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?
None


Debuggability
None


Is this feature fully tested by web-platform-tests?
No
https://wpt.fyi/results/webxr?label=master&label=experimental&aligned

Some items may be trivial enough that testing beyond the webexposed-idl is not worth it.


Flag name on chrome://flags
chrome://flags/#enable-experimental-web-platform-features

Finch feature name
WebXrSpecParity

Requires code in //chrome?
False

Tracking bug
https://crbug.com/1377442

Estimated milestones
No milestones specified


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5072747543920640

This intent message was generated by Chrome Platform Status.

[Rik Cabanier]

Thanks for adding these to Chrome Alex!
Quest browser has been shipping these features for a while and are
being used by authors (using feature detection).

Let me know if you need any help. Setting the framerate was a bit
tricky for us so you might run into the same problems.

> --
> 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/CAGOLbz17HygjLvw97ttrn1Gg4JBQmu2P_h9m4HhPZH%2BCE_kaDQ%40mail.gmail.com.

[Arthur Sonzogni]

Thanks! 

> These include but are not limited to

It's a bit vague to me. Even if you are probably only omitting minor features, it doesn't give reviewers confidence they are not missing reviewing something meaningful.
At some stage before the intent to ship, could you please update ChromeStatus with a document describing exhaustively what this intent is about?

> To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Alex Cooper]

Hi Arthur,

The list at present is exhaustive; however, as we are mainly implementing these slowly over time I did not want to rule out adding minor attributes to be covered by this intent since currently it's just at the intent-to-protoype stage. I intend to ensure accuracy by the time we get to intent-to-ship. By and large we expect these attributes to be very simple (mostly hardcoded to specific values, and/or returning null or no-oping), simply to ease developer burden since as Rik says these attributes are already shipped on the Quest browser. Any features that are going to get a more full implementation we'd either split off or ship the implementation later (albeit potentially only going through the launch reviews and not a full chromestatus launch unless that was deemed necessary since the Web Platform bit was already there).  To that end, a document feels like a bit of an overkill (unless I'm misunderstanding this as a request for a full design document); but I can definitely expand to a more exhaustive list with a description of the bullet of each list.

I'm also unsure where to link such a document on the ChromeStatus.

Thanks,

Alex

> To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.