New issue
Advanced search Search tips

Issue 812247 link

Starred by 5 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

nassh: saved profile connections not showing in omnibox on first attempt

Project Member Reported by e...@google.com, Feb 14 2018

Issue description

Chrome Version       : 63.0.3239.132 (Official Build) (64-bit)
URLs (if applicable) : N/A
Other browsers tested: N/A
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
       Edge:

What steps will reproduce the problem?
(1) Have a saved profile connection in the Secure Shell application.
(2) In the omnibox type 'ssh ' (ssh space).
(3) Type a character (any) from the name of the saved profile connection.
(3.5) Observe that your saved profile connection does not appear in the dropdown.
(4) Press backspace and try again OR wait a few seconds and type a second character OR any other variation to refresh the dropdown list.
(4.5) Select your saved connection from the dropdown as expected.

What is the expected result?
The connection should have been shown in step 3.


What happens instead?
Need to perform some variation on step 4 before the saved connection shows up as an option in the dropdown.

Please provide any additional information below. Attach a screenshot if
possible.

 
step_3.5.png
235 KB View Download
step_4.5.png
186 KB View Download

Comment 1 by vapier@chromium.org, Feb 14 2018

Labels: allpublic
Status: Available (was: Unconfirmed)
Summary: nassh: saved profile connections not showing in omnibox on first attempt (was: Saved profile connections not showing in omnibox on first attempt)
this might be due to profile reading being async, but the omnibox onInputStarted API is synchronous.  if that is the issue, we might be able to address this by adding some communication between onInputChanged so it holds off on calling suggest until it's finished (assuming the suggest callback itself can be done async).

Comment 2 by vapier@chromium.org, Jun 17 2018

 Issue 848307  has been merged into this issue.
Cc: tommycli@chromium.org
 Issue 910692  has been merged into this issue.

Sign in to add a comment