-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best practices for headset and handset AR #96
Comments
Currently the spec mandates that all transient sources have My understanding is that the API is intended to be used by registering against all normal input sources and also adding a transient source listener. Perhaps this can be added to the explainer. /agenda to discuss how authors should be writing this and to see if we need spec or explainer changes to support that |
Another thing to note is that transient sources will most likely be generic-touchscreen |
Here is what I am currently doing, this really does not feel neat.
|
Seems like we need at least the following for it to be usable:
The 1. is a bit concerning from privacy standpoint, but it may be fine (we need to see whether it'd expose more information about the UA / device than the sites already have).
Spec changes are definitely needed - the algorithms for hit test source creation do not take into account whether the input source is transient or not. I don't really want to have 2 different APIs that allow the site to do the same thing (i.e. I want to forbid creating a regular hit test subscription from a transient input source), but that means that unfortunately we'd need to special-case the algorithm for |
Discussed during the 17/11/2020 call created this issue as an action: |
It seems to me the way to go is
targetRaySpace
This would work really well to listen for
selectstart
and do hit testing on whatever input source you get, unfortunately transient input sources are indistinguishable from regular input sources and need to userequestHitTestSourceForTransientInput
and have slightly different options.The text was updated successfully, but these errors were encountered: