Chrome searches Google instead of going to URL
Reported by
daarisd...@gmail.com,
Oct 26
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. type in blg.opentute.com 2. hit enter. What is the expected behavior? Expected to go to the website. What went wrong? Instead, Chrome sends you to the google search result for that URL. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: n/a OS Version: 10.0 Flash Version: Can recreate on multiple other devices, including macOS & Windows. Works fine on Android, it seems.
,
Oct 29
,
Oct 30
daarisdirk@ Thanks for the issue. Tested this issue on Windows 10 and Mac OS 10.13.6 on the reported version 69.0.3497.100, latest Stable 70.0.3538.77 and Canary 72.0.3596.0 and unable to reproduce the issue by following the below steps. 1. Launched Chrome -> entered blg.opentute.com in omnibox and hit enter key. 2. Could observe that the page is redirected to the website. Attached is the screen cast for reference. Request you to update Chrome to the latest Stable 70.0.3538.77, retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Oct 30
Hi, can you provide a screenshot of: 1. What the Omnibox suggestion popup looks like when you type blg.opentute.com 2. Enter the query into the chrome://omnibox debug page and let us take a look at the results. Thanks!
,
Oct 30
,
Oct 31
Does this mean it could be because previously I've actually searched for it on Google? And that's what's causing this behavior?
,
Oct 31
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 31
Thanks for the chrome://omnibox output. It's clear that the omnibox is trying to provide an inline autocompleted to the root page of the hostname plus a #hash fragment. This is bug 879796. It was only fixed for Chrome 71, so it's likely you'll be living with it for a while. One way to fix it would be to delete the visits in your history that autocomplete with a #hash like that, e.g., big.opentute.com/#. It's the #hash that is causing the trouble. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by maans...@gmail.com
, Oct 26