VR keyboard: Orient reticle according to keyboard |
||||||||
Issue descriptionWhen initially introduced, the VR keyboard supplies only a hit point, but not the plane on which the hit occurred. Therefore, the VR UI doesn't have a way to make the reticle planar to whatever keyboard panel it's hitting. Generally this doesn't look too bad, as the keyboard's overall transform is a plane parallel to content. However, when hitting the edges of the keyboard side panels, the reticle is visibly not planar to what it's hitting. One possible workaround is to have the reticle face the user in this situation, similar to what it does when it hits the background bounding sphere. A possible outcome of this bug is also "close and ignore".
,
Apr 19 2018
This will require for the keyboard API to give us a hit plane. Let's lower the priority and see if we actually see complaints that call for re-visiting this.
,
May 3 2018
,
May 4 2018
Amir, claiming this as a UI tech debt task. I've filed this bug against the keyboard: https://b.corp.google.com/issues/79246074
,
Jul 30
This is blocked on a DD change. Disowning for now, and targeting M-71 as this isn't a high priority issue. If we hit M-71 and DD support isn't in place (according to the associated bug), we should probably abandon that issue (and this bug).
,
Aug 1
Hilarious timing. The DD support for this fix just landed, and future versions of the keyboard should report the normal vector. In no way should Chrome require a keyboard update for this, but we can now optionally use the normal if it's available.
,
Today
(20 hours ago)
,
Today
(16 hours ago)
Fixed by DD. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by cjgrant@chromium.org
, Jan 4 2018