Rik Cabanier

> Oh, I was suggesting that we trigger select events _on the layer_, and we extend select events to also contain optional xy parameters when found on a layer. Or...

> What about projection layers? Would that be a special UA case, or left for the page to handle? I think they could handle events like in regular WebXR,

> It also occurs to me that we may not just want select events, but also pointerOver, pointerOut, pointerMove events so that applications can render a reticle. Yes. > Though...

> * You can register an XRRay on the input source, and it's used to trigger select events on the layer. > * You can create LayerHitTestSources with XRRays and...

> Supporting pointer move events might have a problem: that seems more of a performance pitfall (since you're hit testing every frame) compared to select events. I wonder if it...

@Manishearth maybe all we need is a method on XRSession that takes an XRRay (or XRRigidTransform) and synchronously returns what non-projection layer was hit along with the locations in 3d...

Yes, we'll need it for HTML layers as well. I believe the intent is that the UA will draw the controller with pointing rays to make sure that it can't...

Yes, but that choice will be made by the UA. Events for HTML layers will be the regular 2d events but delivered to the elements.

During today's call, we agreed that because this can all be figured out on the client side, there's no pressing need to add this as a javascript API. I will...

@digisomni are you talking about a web browser that is in VR? If so, we will have to define hit testing for WebXR DOM layers.