Re: [w3ctag/design-reviews] WebXR Device API (#403)

@toji 

> [Accessibility] is a large topic, however, and one that we've been seeing more discussion on recently, and so I think it would be more productive for us to outline our current thinking about accessibility in a separate doc which we'll link here.

I believe there was a workshop on XR accessibility recently. Were there any documents produced in that context which might be relevant here?

> > * Could you deep-link to the section in the Spatial Tracking Explainer which explains how to handle getViewerPose() failures?

> I'm not sure exactly what this is asking for? Deep link from where?

Apologies: from the first paragraph of the [Viewer tracking](https://github.com/immersive-web/webxr/blob/master/explainer.md#viewer-tracking) section which links to the Spatial Tracking Explainer - could this instead be a deep link to the relevant section?

> [...] Other examples of how we may use layers in the future: [...]

My [proposed edits](https://github.com/alice/webxr/blob/master/explainer.md) included an ["Important concepts"](https://github.com/alice/webxr/blob/master/explainer.md#important-concepts) section encompassing the concepts I had to draw out as I was reading the explainer and my best guesses as to how to explain them. It would be helpful to have an explanation about layers in your explainer, as well as in this issue thread.

> > When might a session be blurred?
> Having a concrete example in the explainer of when this state might apply would be a good idea [...]

The example you gave here would work well! It doesn't seem to have been worked back in to the explainer yet.

---

One other thing:

Re-reading the explainer, I was confused by this sentence (emphasis added):

> Once drawn to, the XR device will continue displaying the contents of the XRWebGLLayer framebuffer, potentially reprojected to match head motion, _regardless of whether or not the page continues processing new frames_.

What does that last clause mean? i.e. what does it mean for the page to continue processing new frames, if it's not writing to the framebuffer?




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/403#issuecomment-561412741