Entering 'localhost' in the location bar initiates a Google search

VERIFIED FIXED in Firefox 19

Status

()

Core
Document Navigation
VERIFIED FIXED
5 years ago
4 years ago

People

(Reporter: Kyle Kalstabakken, Assigned: abhishek rajput)

Tracking

({regression})

Trunk
mozilla19
regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox18 unaffected, firefox19+ verified)

Details

(Reporter)

Description

5 years ago
When you type 'localhost' in the location bar and hit enter, a Google search is performed.
This also occurs for any number of subdirectories, as long as you don't specify an actual file with file extension (ie, |localhost(/directory/)*|).

I expected to be shown the index page of the site I'm running on my machine. This does work if you type http://localhost

This first happens in the Nightly from Nov 3.

Just scanning the pushlog, it looks like this is caused by:
ded200210541	Abhishek Rajput — Bug 693808 - Make number keywords in locationbar be searched as normal terms. r=jst

... which makes sense because 'localhost' doesn't have any periods, colons or ?s in it. Adding any of these works as expected (eg, 'localhost:80', 'localhost?', 'localhost/index.html')
this is related to bug 150025
Blocks: 693808
Keywords: regression

Updated

5 years ago
tracking-firefox19: --- → ?
Component: Location Bar → Document Navigation
Product: Firefox → Core

Comment 2

5 years ago
Also don't forget about internal network sites.
"myIntranetMachine/Site/" also causes the same problem and is a valid address.

As a note, these problems do not happen with browser.urlbar.trimURLs set to false.
Blocks: 63736
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All

Comment 3

5 years ago
(In reply to João Rosado from comment #2)
> As a note, these problems do not happen with browser.urlbar.trimURLs set to
> false.

They do using today's nightly. TrimURLs has no effect.
No longer blocks: 63736
abhishek, this was caused by your patch and seems like an important issue to resolve. Do you have any ideas how we could address it?
Assignee: nobody → abrjpt
Blocks: 63736

Comment 5

5 years ago
Can we just backout bug 693808 from FF19 before the merge to prevent this from hitting Aurora and then resolve for FF20?
status-firefox18: --- → unaffected
status-firefox19: --- → affected
tracking-firefox19: ? → +
Yep - I'll do that.
Duplicate of this bug: 812116
Duplicate of this bug: 812267
Fixed by the backout of bug 693808.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
status-firefox19: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla19

Comment 10

4 years ago
This regressed again starting with today's nightly.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 11

4 years ago
Oddly, 'localhost' doesn't trigger a Google search, but entering LAN machine names does.

Comment 12

4 years ago
In fact, the bug is even worse than that. It is now impossible with FF to visit a LAN machine. Typing 'http://vega' is automatically changed to http://www.vega.com, and 'vega' initiates a Google search.

Comment 13

4 years ago
Works again with a later build.
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
Tested on: Windows 7x64, Ubuntu 12.10 and Mac OS X 10.8 - using Firefox 19 beta 5. 
Marking as verified fixed. 
If someone is able to reproduce, please reopen it.
Status: RESOLVED → VERIFIED
status-firefox19: fixed → verified
You need to log in before you can comment on or make changes to this bug.