338717 - Search box will not do anything

Status: RESOLVED DUPLICATE of bug 337386

(Firefox :: Search, defect)

Description

[Allan Canush]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060512 BonEcho/2.0a2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060512 BonEcho/2.0a2

When I type something into the search box in Bon Echo alpha 2, and press enter, nothing happens. If I click the magnifying glass, nothing happens. It doesn't even go to the search engine. I end up having to go to Google manually, and that's a big hassle.

Reproducible: Always

Steps to Reproduce:
1.Type something into the search box.
2.Press Enter.

Actual Results:  
Nothing.

Expected Results:  
Searched for the text entered on the selected search engine.

Comment 1

[Patrick]

Does this also happen in Safe Mode?

Can you try with a more recent build? 

Comment 2

[Allan Canush]

1. Still does nothing in safe mode.
2. I'm not sure, but I think this IS the most recent build.

Comment 3

[Ria Klaassen (not reading all bugmail)]

Allan, here is the most recent nightly: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/
Start it up with a new profile (rename the folder Mozilla in Application Data) or create a new one with the profile manager:
http://kb.mozillazine.org/Profile_Folder
This is WFM in any case.

Comment 4

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

I can reproduce this too. But this is not occurred always.

Comment 5

[:Gavin Sharp [email: [e-mail]]]

The problem when using Enter is bug 337386. Allan, do you see any JS console errors if you set javascript.options.showInConsole to true using about:config?

Comment 6

[Greg Bowyer]

I am getting smiler, for me the enter key does nothing the mag glass always works

--> I am waiting long enough for bug 337386 not to apply here 

---
Bon Echo 2.0b1
-- Love the rest of everything done, keep up the nice work

Comment 7

[:Gavin Sharp [email: [e-mail]]]

I'm going to assume this is a dupe of bug 337386, since the original reported didn't reply.

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