Manish Goregaokar

> Taking [OpenXR](https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#XR_FB_hand_tracking_aim) as reference, it also doesn't create an event and instead sets a flag (XR_HAND_TRACKING_AIM_SYSTEM_GESTURE_BIT_FB) if the system thinks there's going to be a system gesture. > >...

Yes, but they also did not make a mutable field :smile: OpenXR has events and frames at its disposal, and it chose frames. We do not have frames at our...

Okay, but magical mutable fields are also error prone since it's never clear what frames this is happening on. It's really counter to our model here: we don't do this...

+1 for having only two modes for the hit test results

@AdaRoseCannon somehow the bot didn't catch that^

Servo is hoping to prototype it for the Hololens, but it's going to take a bit of time. We're hoping to find any rough edges for headworn devices since this...

Yes, to me, personally (not speaking on behalf of all Mozilla people in the WG), I think the API design is good, ignoring the `entityTypes` stuff. I'm a bit concerned...

> A random idea that comes to mind: switching the method to requestHitTestSourceForInputProfile to build on the profiles list that already manifests in the core API surface, returning hits whether...

The bone capsule, as far as I can tell, is something you can theoretically derive by computing poses between spaces. So I don't think we _have_ to expose it, but...

Is there a reason they're offset that way? Is this to provide a useful approximation to a hand mesh?