649004 - browser.urlbar.autofill doesn't function for URLs in history of websites that redirect to the www subdomain unless you type "www." first.

Status: RESOLVED INVALID

(Firefox :: Address Bar, defect)

Description

[Cngevpxhaqrefpber]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

If you go to a website that redirects itself to the www subdomain (such as mozilla.org, which immediately redirects to www.mozilla.org), then the AwesomeBar's autofill (browser.urlbar.autofill) functionality won't autofill when you start typing the URL (such as "moz") unless you precede the URL with a "www."

Reproducible: Always

Steps to Reproduce:
1. Visit mozilla.org -- or another website that redirects itself to the www subdomain (many sites do this) -- a couple of times.
2. Open a new tab and start typing that URL you just visited in the AwesomeBar, without a preceding "www.".  For example, if you went to mozilla.org, type "moz".
Actual Results:  
The URL won't be autofilled/autocompleted in the addressbar, unless you type "www." first.

Expected Results:  
URLs of websites that redirect themselves to the www subdomain should be autofilled/autocompleted in the addressbar regardless of whether or not you prepend a www when typing it, like IE, Chrome, and Opera do.

Right now, about half of the websites I visit won't autocomplete for me in the AwesomeBar unless a I prepend a "www".

Comment 1

[Simona Badau, Desktop QA]

Works fine for me on:
Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110425 Firefox/6.0a1

Reporter, does the issue still occur if you start Firefox with a new, empty
profile?
http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile

Comment 2

[Simona Badau, Desktop QA]

Reporter, please can you confirm whether this issue is still reproducible when you start Firefox with a clean profile? If you no longer have this problem, please set the resolution accordingly.

Comment 3

[Cngevpxhaqrefpber]

Hi, sorry about that, I meant to do this when you first requested it but forgot.

I'm currently on a new, empty profile now and it's still happening.

I went to Archive.org a few times; however, when I type "ar", nothing shows up. When I type "www.ar", then www.archive.org is autofilled.

I went to Google.com and gaming.reddit.com a few times; Google.com isn't autofilled unless I put a www first; gaming.reddit.com isn't autofilled until I type "gaming." (the period is important).

However, after going to slashdot.org (which seems to be one of the few sites these days that doesn't redirect you to WWW), the next time I typed "s" in the awesomebar, slashdot.org is autofilled.

Let me know if you need anything else.

Comment 4

[Vlad [QA]]

Reporter, have you tried to update to the latest Firefox 4.0.1?
http://www.mozilla.com/en-US/firefox/new/

Does the issue still occurs?

Comment 5

[Cngevpxhaqrefpber]

Sorry again for the delayed response; yes, when I made my last comment I was using the latest version of Firefox, v4.0.1.

Comment 6

[Vova Olar]

Fixed in Firefox 6.0 alpha

Comment 7

[Vova Olar]

Fixed in Firefox 6.0 Alpha by bug https://bugzilla.mozilla.org/show_bug.cgi?id=566489
This bug should be closed.

Comment 8

[Chenxia Liu [:liuche]]

I still see this behavior when using the current Nightly build (9.01a), albeit on a Mac, even using a clean profile.

It would seem to me that the autofill will only autocomplete using the entire visited urls, instead of slicing off the common "www" or "http" or "https" prefixes of url strings (which is the behavior I see in Google Chrome, and which I think is the correct UX behavior). The dropdown awesomebar suggestions include the url/page, but autofill doesn't complete in the address bar.

For example: 
1. visit "facebook.com"
2. starting to type "facebook.com" will not autofill
3. typing "w" will autofill "www.facebook.com"
(4. curiously, typing "ww" will eliminate the autofill)

Comment 9

[Marco Bonardo [:mak]]

the new behavior does this, and this bug refers to the old implementation, so it's no more valid.