287697 - JS detection broken

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[a_geek]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 MultiZilla/1.7.0.2b Mnenhy/0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 MultiZilla/1.7.0.2b Mnenhy/0.7

Hello, if I go to the site named above and want to just search for some terms
from the small box, Bugzilla says: "Invalid Bug ID
	  	
'search term' is not a valid bug number nor an alias to a bug number. If you are
trying to use QuickSearch, you need to enable JavaScript in your browser."

I find this quite stupid as I already do have JavaScript enabled, and no
site-specific blocks installed. Also, when I go to the extended search
page and query from there, I get the big "Please stand by..." in the
middle of the canvas which is also JavaScript driven. Since it works
with FF 1.0.2, I assume that somebody "tuned" the JS detection code to
especially **** of users of the suite (it worked for a long time, until
it broke a few weeks ago).


Reproducible: Always

Steps to Reproduce:
1. go to https://bugzilla.mozilla.org using a Mozilla suite browser
2. enter a few words in the search box above the picture of the ant or bug
3. hit 'enter'

Actual Results:  
I get this error message shown above.

Expected Results:  
I expect to get a list of bugs shown, or a page saying "nothing found".

This problem has also hit me on other sites which use Bugzilla. A patch for all
users should be published.

Comment 1

[Matthias Versen [:Matti]]

wfm with 
Mozilla/5.0 (Windows; U; Windows NT 5.2; de-DE; rv:1.8b2) Gecko/20050324

You should try a new (additional test) profile

Comment 2

[Dave Miller [:justdave]]

The error message is a bit misleading.  There are other things besides JS
problems that can cause that error.  What was the actual search terms you
entered that caused it?  It's impossible to troubleshoot this without knowing
what you searched for.  Following the "steps to reproduce" that you provided,
I'm failing to reproduce this.

Comment 3

[a_geek]

My bad - switching to a new profile fixed it. Shame on me! :-((

Comment 4

[a_geek]

I'd still like to know how, and why, upgrading so easily breaks a profile, and
how to fix a profile instead of just deleting it...

Comment 5

[Dave Miller [:justdave]]

(In reply to comment #3)
> My bad - switching to a new profile fixed it. Shame on me! :-((

And that definitely makes it a Firefox bug and not Mozilla. Moving back.

Comment 6

[Matthias Versen [:Matti]]

You could kill the directory profile/chrome/*.* in your broken profile if you
installed extensions.
(This will nuke all Extensions and language packs)