164224 - Bad URL field behaviour

Status: VERIFIED DUPLICATE of bug 135363

(SeaMonkey :: General, defect)

Description

[Lubor Kolar]

I use quick search by Google frequently. I type few words into the URL field and
choose "Search Google for.." command from auto-appearing pull-down menu.
Sometimes I forget to select this pull-down menu command and I press enter on
that words, for example try to write "striped skunk" in the URL field. After
pressing enter Mozilla says "The URL is not valid and cannot be loaded." So I
press down arrow to display pull-down menu, select "Search Google for 'striped
skunk'", but it writes me that error message "The URL is not valid and cannot be
loaded." again, which is wrong. Correct behaviour is to search for string. It
seems Mozilla remembers that first failure because if I cut&paste that string
and select "Search Google for 'striped skunk'" again, it works.

Comment 1

[Rainer Bielefeld]

so it is!
Might be an "automatic search if uri does not start with 'http://' and uri is
invalid or something like that would be a fine enhancment.

For your special "striped skunk - problem": Why do you not simply press the
search-button?

I think, COMPONENT should be "search"
I think, SEVERITY should be "enhancement"

Comment 2

[Lubor Kolar]

I think it is not so good because I usually write urls without http://, but it
could be a cool idea if URL field doesn't begin with protocol name AND contains
spaces, it seems that users isn't typing URL

Why do not press Search button? It's simple, I preffer keyboard and it is faster
for me to write "striped skunk", arrow down, arrow down, enter that write
"striped skunk", search mouse on my table, search pointer on the screen, move
mouse and finally click :-)

I left COMPONENT as it is because I am afraid this is a case of bad URL field
handling (Mozilla does not start the search - is still fighting with URL string
handling)
I set SEVERITY to MINOR because it is behaviour is 100% bad (so it is not an
enhancement, but if we want to implement auto-search when no protocol specified
and string contains spaces, it is minor bug+enhanecement in one).

PS: I am not looking for skunks so often, it was only a sample :-)

Comment 3

[Adrian Ulrich]

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

Comment 4

[Wesha]

v.