For now, go to http://php.net/my , section "Search field suggestions" and check the "hide" box.

Webmaster: we should either maintain a list of non compatible browsers or disable the feature by default (and maybe add a small icon near the search field to activate it). Opinions ?

Thanks for the help!

I sould certainly agree that the feature should be off by 
default if incompatible browser versions cannot be detected 
automatically. Since the script freezes the browser (in the 
case of IE5) before the page even loads there is no way to 
disable the feature.

If you ask me (and you will probably not, because you use IE) - A script should not be able to hang a browser; Especially if it is not designed for that purpose on purpose (infinitive loop - while 1=1, for instance). I recall Firefox recognizing a resource starvation loop, and halting the run, warning me that the page misbehaves, but does not, at any case, hang. It even stops Redirection loops...

You do realize that this is actually a (yet another) bug in IE that Microsoft should (but probably never will) fix...

Shimi: MS stopped Mac IE development.

Webmaster: We need to maintain cacheability of php.net pages, so we need to check the browser in JavaScript, and then if we found the browser to be compatible, we need to load in the library doing the suggestions. This will make the suggestions appear a little bit later for those supporting this feature, but it is doable. We need to look at caching issues of that suggestions JS code though. If we dynamically load it from JS, it might not get cached in not smart enough browsers, and we would end up with too many repeating requests on that file.

You see, I KNEW they're not gonna fix it. :)

Regardless of the bug(?) solution, I strongly suggest the reporter NOT to use a browser that has known security flaws which nobody can stop and cannot be upgraded, because eventually, his computer WILL be compromised.

I do agree with what you are saying, but as a Mac OS9 user 
my choice is pretty limited. I'm stuck with bugs in one 
browser or bugs in another, and none of them are going to 
be upgraded.

I know I know ... I should use OSX ... but that's another 
discussion!

Gabor: 
Why don't we rewrite our script using the idea behind Google Suggest ?
  http://www.google.com/webhp?complete=1&hl=en

This will fix this bug and the caching issue.

Didou: we have a limited and easy to define result set, unlike Google Suggest, plus we don't have the miriad of machines like those behind the Google load balancers. Having the complete result set pushed down to the client (as it is done right now), makes it possible to cache that file, so that it does not even mean a single request later. Using xhmlhttprequest means a *lot of* requests to the server.