Have you tried the auto complete with the space key, or navigating in the list with the cursor keys? Does that work? We had no Safari user to test before....

The dropdown does disappear now if the input field losts focus, this is "by design". It might need to be refined to not disappear if the function list got the focus... I don't have an immediate idea on how one would do this...

First, the dropdown doesn't appear at all in IE5.2/Mac.

In Safari, if I type "arr" into the search field, the 
drop down appears, with all the arr* functions listed.  
If I then press space, the field autocompletes with 
"array ", and I can press return and I'm directed to 
the right page (although, the search field is now 
"array+" ... so you probably need to trim that field).

If, however, I just type "arr" to get the list of 
functions, I should be able to mouse over to one of 
them -- say "array_pad" -- and click it.  When I mouse 
over it, I can see that the link is there (i.e. 
Safari's status bar shows "Go to ca.php.net/
array_pad"), but clicking on the link does nothing 
except make the drop-down disappear.

I realize the JS code is optimized for size, but it 
would be *really* helpful if there was an unoptimized 
version in use during beta testing, so that all these 
bugs could be worked out first. :)

I'm also guessing that this code came from somewhere?  
What is the format of the compressed data?

- Colin

You can find the discussions on the php-mirrors (and partially cross-posted to phpdoc) list about the compression, the code, and why the dropdown is removed after the input field losts focus. The discussion was under the subject "quickref.swf", because I proposed a flash solution initially...

The original thread:
http://www.phparch.com/mailinglists/msg.php?a=360751

One "subthread":
http://www.phparch.com/mailinglists/msg.php?a=360866

Auto-complete doesn't work at all in Safari 1.1 in OS 
10.3

Same result as the original poster with Konqueror 3.1.4 
(Mandrake 9.2) (but then, Konqueror and Safari are based 
on the same layout engine): clicking on a function doesn't 
fill it in in the text box. Navigating with cursor keys 
and autocompletion with space don't work either... 
 
The dropdown box does look nice though :)

The functions listed in the dropdown are now clickable, so you can get to that function page directly. It would be nice if some Safari user would be able to find out what point that space is inserted into the input field. Note that event handlers are supposed to return false in case they handled the event properly, and no action is needed. We do return false in case we handle the spacebar action...

I can only wait for feedback on the questions raised, since I have no access to a Safari browser.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.

Hrmm ... I did provide feedback for this, but I don't 
know why it isn't in the bug database.

Anyway, this is what happens: I go to the search page, 
and type in "hex", which narrows the choice of functions 
down to one: "hexdec".  I then type space, which 
completes the function name, but also adds my space 
(i.e. "hexdec " is in the field now).

If I press enter, the search still works. However, the 
search field now says "hexdec+", presumably because the 
space got urlencoded, passed along, and never urldecoded 
and/or trimmed.

This happens in Safari 1.1.1, with OX 10.3.2.

- Colin

The search code significantly changed recently, which disallows any space in the input field in many browsers. Since I have no Safari to test, please test again with the latest code on a mirror, and confirm if it works now or it is still buggy.

Still works as I described yesterday (tested on my 
mirror: ca.php.net).

This seems to have been fixed now ... either by a change 
to the code, or in Safari 1.2 (which I now use).

Either way, I suppose you can close this bug.

n/m ... i can close it