Pressing the app button should bring up the omnibox.
Exact behaviour and appearance of the omnibox (and associated ui elements) will be defined in the HTML5 UI.
Working plan as of September 8 is to group the omnibox within the toolbar, ala desktop and mobile. Behavior of the toolbar will be as described above (press app button to show/hide). The toolbar will automatically show during site-to-site transitions, and hide once loading is complete (timing TBD).
We're waiting to hear back on results from Feb 1 user testing session, but tentatively the plan is:
* Loading indicator appears during site transitions. It displays same information as Chrome for Android omnibox would during transition, but is inert. It cannot be clicked, interacted with, etc.
* Interactive omnibox is available inside menu mode. It is visually distinct from the loading indicator.
We may want to split these into distinct bugs. We should hold off until we get that feedback from user testing, though.
On splitting bugs:
- The URL indicator already works, and is no longer referred to as an Omnibox.
- The very basic Omnibox has landed, and appears in the new menu mode screen.
I've made bugs to track:
- Enabling and verifying all the basic elements in WebVR (as opposed to VR shell): crbug.com/687960
- Omnibox refinement and styling: crbug.com/683344
- Toolbar on WebVR site-to-site: crbug.com/645135
Once the VK lands, I'd like to close off this bug. In addition to the issues above, we should file new, much more specific issues to track omnibox improvements.
Comment 1 by girard@chromium.org
, Aug 26 2016Status: Available (was: Assigned)