feat: Split WebXR and WebVR #5064
Conversation
|
Yeah, seems like the right thing to do. Thanks! |
|
Looks like XR data needs some updating... the numbered notes should probably be removed and I'm not seeing support in Chrome 76. |
| "76":"y", | ||
| "77":"y", | ||
| "78":"y", | ||
| "79":"y" |
There was a problem hiding this comment.
Anything before 79 should be "n". The same would apply for Android Chrome and Android WebView. (I don't know how you do those.)
There was a problem hiding this comment.
https://www.chromestatus.com/feature/5680169905815552 says 76, so… ¯\_(ツ)_/¯
There was a problem hiding this comment.
It says 'origin trial'. That means that individual sites would require a token to activate the API. Origin trial tokens will be unavailable when the API ships in 79.
| @@ -0,0 +1,368 @@ | |||
| { | |||
| "title":"WebXR Device API", | |||
| "description":"API for accessing virtual reality (VR) and augmented reality (AR) devices, including sensors and head-mounted displays.", | |||
There was a problem hiding this comment.
This definition ignores AR use cases which have applications outside of games. The spec was designed specifically (so it's author tells me) to address a spectrum of immersion so that a site could use as little or as much immersion as it wanted. See my article for more on that.
| ], | ||
| "bugs":[ | ||
| { | ||
| "description":"WebXR is in development and is still changing. WebXR was formally developed as WebVR. Because of this there could be bugs inside the standard of the W3C." |
There was a problem hiding this comment.
WebXR was formally developed as WebVR.
There's some historical truth to this. The spec has evolved so much in more than two years that I'm not sure it's relevant to users of the API. Neither Google nor MDN feel the need to mention this in WebXR documentation.
Because of this there could be bugs inside the standard of the W3C.
What does this mean?
| "2.5":"n" | ||
| } | ||
| }, | ||
| "notes":"For a WebXR experience a head mounted display (VR HMD) is required.", |
There was a problem hiding this comment.
Not true. Look at XR.requestSession() and XR.supportsSession(). The API supports a session mode called "inline" with which content can be rendered in a page.
|
I've updated the feature data with help from @jpmedley's comments and made the feature available on the site now. For any further suggested changes please submit a new PR. Thanks all! |
Chrome 79 has removed support for WebVR.
Without this, it’s impossible to display this in the “Can I use…” data.
Reverts: #4456
See also: #3948
/cc @jpmedley