Issue metadata
Sign in to add a comment
|
nassh: doesn't auto-complete profiles correctly in URL bar |
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. Open a new tab 2. Type "ssh <profile_name>" in the url bar 3. saved profiles do not autocomplete What is the expected behavior? The saved profiles should auto complete. What went wrong? It seems like there's some caching problem. When I first create a new tab and type "ssh kak" (kak is the name of my saved SSH profile), the profile auto complete doesn't work. Subsequent tries do show the auto complete correctly though WebStore page: Secure Shell App v0.8.43 Did this work before? Yes A few months ago? Chrome version: 66.0.3359.181 Channel: n/a OS Version: OS X 10.13.4 Flash Version:
,
Jun 1 2018
Tested the issue on chrome reported version 66.0.3359.181 using Mac 10.12.6 with steps mentioned below: 1) Launched chrome reported version and installed Secure Shell App extension from web store, URL: https://chrome.google.com/webstore/detail/secure-shell-extension/iodihamcpbpeioajjeobimgagajmlibd?utm_source=chrome-ntp-icon 2) Signed into chrome from Chrome://settings 3) Opened NTP and entered " ssh Test B", here Test B is the profile name, observed "Unable to parse destination: Test%20B" @Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging. If possible could you please provide screencast of the issue which helps us in better understanding the issue. Thanks!
,
Jun 3 2018
This clip illustrates the bug. I have a profile named 'kak', and the first time typing "ssh kak", the profile doesn't appear. Then I hit escape, and tried it again, and the profile appears (and I'm able to connect).
,
Jun 3 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 4 2018
Tested the issue using #66.0.3359.181 on Mac 10.13.3 as per the steps mentioned below. Steps: 1. Launched Browser 2. Signed into chrome from Chrome://settings 3. Installed Secure Shell app @Reporter: Could you please find the below screencast and let us know the update if possible please update Chrome to latest version #67.0.3396.62 and check if you still face the issue? Thanks!!
,
Jun 17 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, May 31 2018