localhost URLs not manually editable
Reported by
gggkill...@gmail.com,
Sep 26
|
|||||||||||||||||
Issue descriptionChrome Version : 69.0.3497.100 (Official Build) (64-bit) (cohort: Stable) Revision : 8920e690dd011895672947112477d10d5c8afb09-refs/branch-heads/3497@{#948} URLs (if applicable) : http://localhost:9091/transmission/web/#confirm and http://localhost:8082/dashboard/#/ Other browsers tested: Safari: Untested Firefox: OK Edge: OK What steps will reproduce the problem? (1) Go to either one of the URLs specified above (you'll need to have Transmission installed for the first. The other URL is from an proprietary program) (2) Attempt to delete the "#confirm" or "#/" part of the URL What is the expected result? Chrome loads the localhost URL. What happens instead? Chrome searches for the localhost URL (even when "http://" is prefixed to it). Screenshots attached below. First 3 are about "http://localhost:9091/transmission/web/#confirm" and the last two are about "http://localhost:8082/dashboard/#/"
,
Oct 1
,
Oct 1
Can you post your about:omnibox data for one of the edited strings, with "show all details" checked?
,
Oct 1
This can sometimes happen (due to bug 648355 that has been fixed but the fixes haven't made it into Chrome 69) if you have a custom search engine associated with localhost. Do you? (I think the answer is yes, judging by the DuckDuckGo labels in the screenshots.) If so, it help to know the exact pattern used in the custom search engine.
,
Oct 1
> Can you post your about:omnibox data for one of the edited strings, with "show all details" checked? I have attached a full-page screenshot in the attachments (I don't know of a better way to provide the results so I apologize if it's not enough). > This can sometimes happen (due to bug 648355 that has been fixed but the fixes haven't made it into Chrome 69) if you have a custom search engine associated with localhost. Do you? (I think the answer is yes, judging by the DuckDuckGo labels in the screenshots.) If so, it help to know the exact pattern used in the custom search engine. I do indeed have a custom search engine, unfortunately I'm unsure of how to confirm if it's associated with localhost or not. The exact pattern in use is https://duckduckgo.com/?q=%s
,
Oct 1
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
,
Oct 1
Thanks for the quick reply. Can you re-post about:omnibox data for the input "http://localhost:9091/transmission/web/"? This time check both "show all details" and "prevent inline autocompletion". Also, can you check your search engine list to see if any have localhost in the pattern? Settings -> Manage search engines -> use the search box on that section to search for "localhost" thanks!
,
Oct 1
Hello, I have no search engines with the "localhost" pattern (as shown in the second attachment) and the about:omnibox data is in the first attachment.
,
Oct 1
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
,
Oct 1
Ah, thanks for the output. It looks like this is a duplicate of bug 879796, which was fixed in later version. |
|||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Sep 26