New issue
Advanced search Search tips

Issue 726745 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Migrate VR URL bar to use OmniboxView and related classes

Project Member Reported by cjgrant@chromium.org, May 26 2017

Issue description

The 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
 
Labels: -M-61
Owner: cjgrant@chromium.org
Status: Started (was: Available)
I know that at least some of this is in progress. Not sure how much that remains is still valid or when it could be realistically delivered. Removed the M-61 label for the time being.
Status: Assigned (was: Started)
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.
Status: Available (was: Assigned)
Owner: ----
Owner: cjgrant@chromium.org
Status: Assigned (was: Available)
 Issue 683344  has been merged into this issue.
Labels: -Type-Bug Type-Task
Status: WontFix (was: Assigned)
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