Issue metadata
Sign in to add a comment
|
.test domain triggers a search instead of going to the domain
Reported by
qro...@gmail.com,
Feb 23 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Type in something.test in the url bar What is the expected behavior? The browser tries to resolve something.test What went wrong? The browser does a search for something.test Did this work before? N/A Chrome version: 64.0.3282.167 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Adding http:// before something.test causes the browser to try to resolve the domain. After the .dev tld was sold, I read that dev sites should be on .test or .localhost. When I tried .test the browser didn't seem to support it.
,
Feb 26 2018
qrokqt@ Thanks for the issue. Tested this issue on Windows 7, Mac OS 10.12.6 and Ubuntu 14.04 on the latest Stable 64.0.3282.186 and able to reproduce the issue. Issue seems to be fixed on the latest Beta 65.0.3325.88 and Canary 66.0.3355.0. Below is the reverse bisect information: Reverse Bisect Information: =========================== Good Build: 65.0.3301.0 Bad Build: 65.0.3300.0 Marking the status as Untriged and will update the changelog URL tomorrow by executing the per-revision script. Thanks..
,
Feb 27 2018
//Adding to comment #2. Reverse Bisect Information: =========================== Good Build: 65.0.3301.0 (Revision - 525885) Bad Build: 65.0.3300.0 (Revision - 525555) Unable to provide the Changelog URL by executing the per-revision script as all bad builds were invoked. Tried increasing the Good build range as well but no luck. Hence provide the changelog URL from Omahaproxy. Manual Changelog URL: ===================== https://chromium.googlesource.com/chromium/src/+log/65.0.3300.0..65.0.3301.0?pretty=fuller&n=10000 From the above Changelog, suspecting the below change: Reviewed-on: https://chromium-review.googlesource.com/831214 dschuyler@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Thanks..
,
Mar 12 2018
This sounds like a duplicate of this bug: crbug.com/782146 . If so, this should be fixed in version 66.xxxxx, which iiuc should be out in late April. qrokqt@gmail.com, you may want to try out an early version of Chrome version 66 (on Windows for OSX) from https://www.google.com/chrome/browser/canary.html or wait for that version to be released. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Feb 25 2018