Alex Cooper

Thanks! Pitor is out for a couple of weeks; so I'm posting planned explainer changes here as well to help facilitate this conversation while I work on the PR/figure out...

> So I'm pretty comfortable with how XR rendering works as I helped review the original WebVR APIs while serving on the TAG. With that background, I am a bit...

Thanks Alex. While I agree that there may be many sensors that make up an AR session, I think that doesn’t preclude the ability of an AR Session to “lock”...

Correlating what piotr says, I'm only seeing depthNear and depthFar defined for XrRenderState(Init), which is specced: https://immersive-web.github.io/webxr/#xrrenderstate-interface, in case you maybe had some inheritance chain somewhere.

Discussed this in the meeting today; it sounds like my assertion that no one was using this was wrong and that Meta may be doing so. However, they answer for...

For full clarity, this is the portion of our spec that I'm discussing: https://immersive-web.github.io/webxr/#permissions (Currently 14.2)

Regardless of Rik's findings; I believe we need to move the "permission request algorithm" portion of the spec; since that is no longer supported by the Permissions API, though it...

As it stands today then it *also* sounds like you ignore our current spec of parsing through and replying with the state of requested/optional features? You *only* take a generic...

The spec as written currently requires parsing through and listing if all required/optional features are enabled or not, the "permission query algorithm" (Can't link since it's a link to the...

And would bringing up the 2D browser then allow navigation (I'd guess not as that would cause the session to unload)? Or switching tabs? It seems very much like trying...