Re: [w3ctag/design-reviews] WebXR Hit Test Module (#463)

One important issue here is that a better job needs to be done in WebXR specs and docs to clarify the difference between "hit testing" in the context of using ray casting with sensors to detect intersection with _real-world_ objects vs. using virtual ray casting to determine intersection of a ray with virtual objects in the scene. These are very different concepts, and it actually took me quite a while to realize that the phrase "hit testing" in the WebXR specs was referring to real world, not virtual world, hit testing.

I am curious what the long term usage of virtual vs real-world hit-testing will be in terms of which will be most common; I suspect that once XR devices are commonplace _and_ VR is the primary use case rather than AR, we will find that virtual hit testing is by far the more common scenario. Regardless, it's worth considering this issue when naming and describing this capability, and I would at least suggest renaming the spec to something more like "WebXR Physical Target Hit Testing" or something related to the real world.

-- 
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/463#issuecomment-635440090