Side-comment: the keyboard/page overlap is by design. Keyboard is designed to sit at roughly waist height. Because of VR's narrow FOV, the page should not be positioned above the keyboard, since this would cause the user to have to crane their neck up almost vertically to see the input field.

Separately, the issue reported (invisible region that extends beyond the actual visible keyboard) does sound like a bug.

Doug, can we clarify "much farther into the item"?  There is certainly an invisible border around the keyboard, that I'd quantify as approximately the height of the keyboard's 'e' character.  Is that what you see?

I'm not sure if there is a specific reason for this border - I'll ask.

b/74250436 is now open against this.  xiaotao@ has confirmed there's a border all around the keyboard, but needs to investigate why.

Yes about the height of  the 'e' character or approximately 1/3 of the visible item is not clickable.  It seems like a pretty thick invisible border.

Agreed that padding is a separate issue (maybe its there to avoid reticle jumping, but its weird for the keyboard to do that).

The keyboard/page overlap may cause annoyance to the user. For example in this case, certain list items may be unreachable. The user may hit the app button to hide the keyboard, but then we decided to also unfocus the field, and a page my tie the dropdown to focus, in which case they would also hide the list items. 

Separately, we also don't do the "scroll into view"like we do on Android, so a field at the bottom will spawn the keyboard, but the keyboard my obscure the field.

Gordon, do you see any easy fix for such cases? 

The solution is detailed in the original chromevr-1.0 spec, but has been scoped out of MVP and is part of MVP-NEXT.

From the spec:
> additional affordances are planned for subsequent releases — like automatically zooming and scrolling form controls into view on focus. Wherever possible, input element is zoomed until it meets minimum text size according to Daydream design guidelines (24dmm). If overlap would cover input area, the input area is panned into view by the UA.