78404 - Autocomplete shows invalid matches.

Status: VERIFIED DUPLICATE of bug 87667

(SeaMonkey :: Autocomplete, defect, P3)

Description

[Jesse Michael]

Using a cvs build from today (pulled May 1, 2001 around noon PST), if I type
"www.b" in the url bar, instead of getting only urls from my history that start
with "www.b", i also get lots of sites that start with only "b" like
"bugzilla.mozilla.org".

Comment 1

[timeless]

.

Comment 2

[Oliver Klee]

Confirming on 2001043004 Win2k, setting OS=All.

Comment 3

[Alex]

Are we just talking about typing "www.b" to get "bugzilla..." with no preceeding
"www," or does this also include the opposite behavior where you type "b," with
no preceeding "www", and get something like "www.bonsai..."?

The second behavior I described should not be considered a bug, IE does this too
and it's more streamlined not to type "www" first just to trigger the autocomplete.

Comment 4

[Alec Flett]

cc'ing hewitt.
This might be tricky - I know we're doing stuff such that "ya" matches
"www.yahoo.com" and that "www.ya" matches "yahoo.com", but we need to make sure
that if we're chopping off any prefix like "www.", that we only match against
domain names... which will be especially tricky for intl domains, like www.foo.co.uk

Given the trickyness of this, I'm setting this to moz 1.0 but I sure hope hewitt
gets some cycles to tackle it :)

Comment 5

[Tom Mraz]

Reporter clearly states that he (me too) gets wrong matches (starting with b)
when typing www.b. So the opposite - getting matches with www.b when you type b
isn't the reported bug and is surely correct.
Please fix the reported bug sooner than moz 1.0.
It shouldn't be so hard to do it because the whole typed string should be
substring of the match. I don't know why anyone would like to have www.ya
matching yahoo.com. 

Comment 6

[Blake Ross]

--> Autocomplete

Comment 7

[Casey Perkins]

The problem I just spotted falls under the same category of invalid matches, but
I think it might should be filed under a different bug. You can tell me that you
think.
I was going to www.javascriptsource.com. After having typed "www.javascript", I
was presented with matches such as this:
javascript:parentAds_fnblahblahblah(blahparameter)
These are URLs I have never typed. What they are, I suppose, are the javascript
URLs of clicked links that execute whatever Javascript function.
Now the fact that something starting with "javascript" should appear upon typing
"www.javascript" does fall under this bug.
But what about this: If I do choose one of this links, nothing happens. Why?
They aren't valid links, because I'm not on the web page that contains the
referenced function. Links that can't do anything shouldn't be shown. That would
include most if not all links starting with "javascript:" (although I still want
my javascript debugger to appear as in 4x when I type this, but alas, that's
another gripe, another time).

Comment 8

[Joe Hewitt (gone)]

*** This bug has been marked as a duplicate of 87667 ***

Comment 9

[Tom Mraz]

Verifying based on comments and test with Linux 2001091121