Mozilla 1.7b - String in location bar that appears in search drop down does not get searched after ENTER or RETURN

RESOLVED WORKSFORME

Status

SeaMonkey
Location Bar
RESOLVED WORKSFORME
14 years ago
9 years ago

People

(Reporter: k.booth, Unassigned)

Tracking

Trunk
PowerPC
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040218
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040218

In 1.7b, a string in the location bar is not searched, instead the browser
treats it as if a URL string. An error message is eventually returned reporting
a bad URL.

Reproducible: Always
Steps to Reproduce:
1.Enter string in location bar
2.With mouse, click on location bar string in search drop down
3.

Actual Results:  
Error message reporting bad URL

Expected Results:  
A search should have been performed on the string in the location bar that
appeared in the search drop down.

Mozilla ver 1.7b
Theme: Classic
Mac configuration: 10.3.3; 15" AL PB, 1.25GHz, 1.25GB RAM
Which Search Enigne do you configured ?
Have you tried to reset the search Engine ? (edit\preferences\Navigator\Internet
Search

BTW: You can also enter a search string and use the arrow up key + Return
(Reporter)

Comment 2

14 years ago
At suggestion of matti-at-mversen.de, I changed the search preference from ASK
JEEVES to GOOGLE and the search on location bar entry in the drop down line
works as expected. Not sure if this is a defect with Mozilla 1.7b or the way it
interacts with ASK JEEVES.
And if you switch back ?
My "Ask Jeeves" search works as expected...
(Reporter)

Comment 4

14 years ago
When switching back to ASK JEEVES the search function works properly in the drop
down location bar.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
This can happen if you upgrade, resetting the engine should always fix that
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.