Autocomplete doesn't list any URLs for "www."



Location Bar
14 years ago
9 years ago


(Reporter: Alex Pircher, Assigned: Andrew Schultz)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616

If you type "www" into the locationbar the Autocomplete-Feature lists all
URLs beginning with "www". However, if then you add a point (".") to "www"
no URLs are listed anymore. Only if you add an additional character the URLs
are listed again.

Reproducible: Always
Steps to Reproduce:
1. Type "www." in the locationbar

Actual Results:  
No URLs beginning with "www." are listed

Expected Results:  
URLs beginning with "www." should be listed

Comment 1

14 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10


Comment 2

14 years ago
Just tried with Mozilla 1.7.3, same behavior. After typing the point
all entries disappear.

Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.3) Gecko/20040910

Comment 3

14 years ago
Just discovered something that might help!
Typing anything other than "www." e.g. "bugzilla." in the locationbar
brings up the list of URLs starting with that string.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED

Comment 6

13 years ago
Same behaviour under WinXP with 1.7.12
Resolution: EXPIRED → ---


13 years ago
Assignee: location-bar → ajschult
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All

Comment 7

13 years ago
Created attachment 204656 [details] [diff] [review]
simple is better

This compares the two strings, compares again without the protocol and compares again without the host prefix.  This should actually be faster since it avoids invoking nsSubstring.Cut (twice per history URL).
Attachment #204656 - Flags: review?(iann_bugzilla)

Comment 8

13 years ago
4252       // make a copy of the value because AutoCompleteCompare
4253       // is destructive
4254       nsAutoString url;

Since AutoCompleteCompare is no longer destructive, |url| can be an nsDependentString, right?


13 years ago
Attachment #204656 - Flags: review?(iann_bugzilla) → review?(cbiesinger)
Product: Core → SeaMonkey
Comment on attachment 204656 [details] [diff] [review]
simple is better

I'm clearly not going to get to this and it's probably outdated now anyway
Attachment #204656 - Flags: review?(cbiesinger)

Comment 10

9 years ago
It is working in SeaMonkey 2.0 RC 1, so it seems that it has been fixed meanwhile. Closing this bug.
Last Resolved: 13 years ago9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.