357722 - Url autofill does not work when enabled in FF 2.0

Status: RESOLVED DUPLICATE of bug 303145

(Firefox :: Address Bar, defect)

Description

[Geert Diels]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

browser.urlbar.autoFill true does not work correctly. For example when you type an url www.cnn.com and the next time you type cn autofill does not work. In version 1.5 this worked perfect.
This also happens with other url's.

browser.fixup.alternate.enabled (true)
browser.fixup.alternate.prefix (www.)
browser.fixup.alternate.suffix (.com)
are set correctly.

Reproducible: Always

Steps to Reproduce:
1. in url type www.cnn.com
2. type cn ==> no autofill
3.




http://forums.mozillazine.org/viewtopic.php?p=2553584
http://forums.mozillazine.org/viewtopic.php?t=470342
http://forums.mozillazine.org/viewtopic.php?t=468608

Comment 1

[Don Erway]

Confirming this here too.

When you type in the location bar, you can see the right possibilities come up in the drop down menu, but frequently it does not autofill.

I find you have to type either http://... to get it to actually autofill, or you have to type the entire qualified name.

Comment 2

[valaszoljnekem]

I can confirm that it works randomly, I see no rule for what URLs works and for what doesn't. 
Very annoying bug.

Comment 3

[Sam]

I can confirm that this is a problem.  I used inline autocomplete a lot in FF 1.0 and 1.5, and it worked great.  Now it doesn't work, unless the address never has a "www" in it.  

For example, typing "a" brings up abcnews.com properly, since there is no www in front of it at the default abcnews site (anandtech.com works too for this reason).  

But typing "c" does NOT bring up cnn.com, because cnn.com goes immediately to WWW.cnn.com.  So, unlike FF 1.5, I now have to type "www.c" to bring up cnn.com in the inline autocomplete.

VERY annoying bug.

Comment 4

[Sam]

Strictly speaking, it is the *inline* part of the inline autocomplete that isnt't working.

Comment 6

[Nikitas Liogkas]

(In reply to comment #5)
> 
> *** This bug has been marked as a duplicate of bug 303145 ***
> 

I don't think this is a duplicate of bug 303145. That bug has to do with the 'www' prefix, while this one simply states that autofill doesn't complete the best match inline, regardless of whether there is a 'www' in that best match.

Comment 7

[Don Erway]

This is not a duplicate!

This is a bug in 2.0, that was not in 1.5!!!

Duping it to a bug, which has been declared "won't fix", is not helpful.

Please re-open this bug.