400012 - Domain Guessing does not work any more when Internet Keywords enabled.

Status: RESOLVED WONTFIX

(SeaMonkey :: Location Bar, defect)

Description

[Johannes Leushuis]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4

Domain Guessing does not work any more ever when Internet Keywords are enabled. So typing "netscape" in the location bar will never direct you to www.netscape.com any more. I think this is wrong. When domain guessing is enabled and only one word is typed in the location bar then a domain check with www and .com should be done. If the domain does not exist, then Internet keywords should be used.

Reproducible: Always

Steps to Reproduce:
1. make sure in the Preferences Domain Guessing and Internet Keywords are enabled
2. type a company name, like netscape, in the location bar, without www and .com
3. hit return
4. it will never ever direct you to www.netscape.com
Actual Results:  
It searches Google for netscape and gives you the results

Expected Results:  
Showing the home page of www.netscape.com

Comment 1

[Serge Gautherie (:sgautherie)]

Can you reproduce with SeaMonkey v1.1.9 ?

Comment 2

[Johannes Leushuis]

Yes, I can reproduce in Seamonkey 1.1.9

Comment 3

[Serge Gautherie (:sgautherie)]

(Filter "spam" on 'prefs-nobody-20080612'.)

Comment 4

[Tony Mechelynck [:tonymec]]

I think this is a known problem, but I cannot find it back.

Comment 5

[Phoenix]

Confirming issue, when both "Add www. and .com to the location if a web page is not found" and "Perform a web search when entered text is not a web location" settings checked in Preferences - Browser - Location Bar - Unknown Locations. Seems that web search have higher priority, which doesn't looks right.
Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a1) Gecko/20111017 Firefox/10.0a1 SeaMonkey/2.7a1

Comment 6

[Will Budreau]

A friend who just upgraded to FireFox 12 reported this to me.  The only workaround I found was to set keyword.enabled to false, which now means the awesome bar is a lot less awesome. (He can live without keyword search.. I can't)

Comment 7

[Philip Chee]

> A friend who just upgraded to FireFox 12 reported this to me.
Will, this is a SeaMonkey bug. You'll need to look for the equivalent bug in Product=Firefox.

Comment 8

[Will Budreau]

Thanks, filed bug 760836