Closed
Bug 424170
Opened 16 years ago
Closed 16 years ago
AwesomeBar Should Go To First Search Result when Hitting Enter
Categories
(Firefox :: Address Bar, defect)
Firefox
Address Bar
Tracking
()
RESOLVED
DUPLICATE
of bug 410837
People
(Reporter: chrisjf, Unassigned)
Details
Attachments
(1 file)
35.07 KB,
image/gif
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4 When I type a word in the Location Bar/AwesomeBar and then hit enter, Firefox should go to the first result of the AwesomeBar instead of doing a Google "I'm Feeling Lucky" search for that word. I use the AwesomeBar now way more than I use Google I'm Feeling Lucky search.(Thank you Firefox 3 betas!) If I want to Google search something I'll just use the Google Search box to the right of the Location Bar. I find that pressing the down-arrow-key and then the enter key is an extra unnecessary step. The default behaviour of the Location Bar/AwesomeBar should be to just go to the first result when I hit enter. Get rid of the down-arrow-key step. Note: Safari does this already. If you start typing "bug" in Safari and then hit enter, Safari will go to the first suggested result of the Location Bar. Reproducible: Always Steps to Reproduce: 1. Type your favourite word into the AwesomeBar/Location Bar i.e. bug 2. See the list of logical suggested sites from your Bookmarks and History. 3. Hit the Enter key and be magically transported to a random website because of a Google I'm Feeling Lucky search. i.e. http://www.imdb.com/title/tt0470705/ Actual Results: Firefox does a Google I'm Feeling Lucky search. Expected Results: Firefox should take me to the first result on the list (suggested by the AwesomeBar) when I hit Enter. Instead, I have to press the down-arrow-key and then hit enter.
Reporter | ||
Comment 1•16 years ago
|
||
This is just a visual example of the problem.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
(In reply to comment #2) > > *** This bug has been marked as a duplicate of bug 186136 *** > commented there
Updated•16 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•