Closed
Bug 147667
Opened 22 years ago
Closed 22 years ago
location bar search doesn't work after accidentally trying to use search terms as url
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 135363
People
(Reporter: sockbot, Assigned: hewitt)
References
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 BuildID: 2002052306 Sometimes when I want to use the url bar to search google, I press enter instead of pressing tab/down arrow to select "search google". when mozilla says that it couldn't find the domain i requested, i can't use the keyboard to re-enter the search properly from the drop down menu. using the mouse and left clicking works fine. Reproducible: Always Steps to Reproduce: 1. Enter some search terms into the URL bar ie, search terms 2. Press Enter 3. When http://search terms/ is not found, press alt-tab to go back to the URL bar 4. Use the keyboard to select "search google for search terms" 5. Press Enter Actual Results: Mozilla tries again to go to the site http://search terms/ Expected Results: Mozilla should redirect to google or equivalent. In this case, using the mouse to select from the drop down menu works, but keyboard operation only does not. Have not tried with other search engines besides google.
Comment 1•22 years ago
|
||
*** Bug 149939 has been marked as a duplicate of this bug. ***
Comment 2•22 years ago
|
||
*** Bug 149548 has been marked as a duplicate of this bug. ***
Comment 3•22 years ago
|
||
*** Bug 140268 has been marked as a duplicate of this bug. ***
Comment 4•22 years ago
|
||
*** Bug 147858 has been marked as a duplicate of this bug. ***
Updated•22 years ago
|
URL: http://n/a
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: using keyboard to use built in search function doesn't work when tried after accidentally entering search terms as a url → location bar search doesn't work after accidentally trying to use search terms as url
Comment 5•22 years ago
|
||
*** Bug 151268 has been marked as a duplicate of this bug. ***
Comment 6•22 years ago
|
||
*** Bug 152686 has been marked as a duplicate of this bug. ***
Comment 7•22 years ago
|
||
The URL bar search functionality is really cool, but I often forget to press the down arrow for Google and get caught in this trap. A nice usability enhancement would be to make search the default whenever the text typed in the URL bar includes a space, which shouldn't appear in a URL.
What about making search the default if the text typed does not contain a period? Not all search terms will be two or more words, but I believe the period is ignored in google searches. Would this adversely affect double-byte character sets, such as big5 Chinese?
Comment 9•22 years ago
|
||
> What about making search the default if the text typed does not contain a
period?
A single word input without periods or spaces is a perfectly valid hostname,
e.g. 'localhost'. It would probably not be a good idea to make search the
default behaviour in this instance as most networks with DNS configured access
machines directly by hostname, and would then be required to type "http://"
before any local domain request.
Comment 10•22 years ago
|
||
I'd say, it would be enough, if Mozilla recognizes search by spaces. Because if you only type one word Mozilla adds www. at the beginning and .com at the end. So you get a failure message or see (probably) the homepage you searched for ;-).
Comment 11•22 years ago
|
||
This is a dup of bug 135363. I'm proposing a patch to it - which should solve this bug too... :-)
Comment 12•22 years ago
|
||
*** Bug 147705 has been marked as a duplicate of this bug. ***
Comment 13•22 years ago
|
||
*** Bug 154714 has been marked as a duplicate of this bug. ***
Comment 14•22 years ago
|
||
*** Bug 156335 has been marked as a duplicate of this bug. ***
Comment 15•22 years ago
|
||
*** This bug has been marked as a duplicate of 135363 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•