Migrate VR URL bar to use OmniboxView and related classes |
|||||||
Issue descriptionThe initial VR browser is using a read-only URL indicator, offering no input or suggestion capabilities. When we move to a more complete omnibox implementation, existing common Omnibox classes (OmniboxView, ToolbarModel, etc) must be used. We'll have to figure out: - How to let the omnibox work synchronously with the VR GL threading scheme - How to a manage two instances of the omnibox (Clank + VR) - Whether we can leverage Chrome Views in any way
,
Jul 19 2017
I wouldn't consider the ToolbarModel work to address this, although it's a start. Returning this to non-started to avoid giving the wrong impression.
,
Jul 20 2017
,
Jul 20 2017
,
Aug 9 2017
,
Aug 11 2017
Issue 683344 has been merged into this issue.
,
Oct 4 2017
,
Oct 10 2017
With the current UX outlook on Omnibox, it looks like our UI will become a client of AutocompleteController, but not OmniboxView. Closing this off. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by vollick@chromium.org
, Jul 10 2017Owner: cjgrant@chromium.org
Status: Started (was: Available)