Tried this in a a few different templates and in both IE for the mac & IE on Windows 2000. Keep running into the same problem.
Got this report from my client:
"When we type anything (ex. Afghanistan) in IE search box, there are no results. It seems like the string is not passed at all. The stranger part is that if we just clicked on the submit with the default text (search text) in there, IE does produce results."
I only use Windows through Browsercam, but was able to find similar results in IE for the Mac and Windows. This all works just fine in Firefox and Safari btw.
However, in IE for Windows if you search for a term (say 'ThisDoesNotExist') which isn't found the function search_view() doesn't seem to recognize the $_POST['op']. It doesn't seem to send people to:
http://www.example.org/search/node/ThisDoesNotExist
but rather to:
http://www.example.org/search/node/
It does seem to work fine if you search from the default search box that appears in the content here:
http://www.example.org/search/node/
But fails if you use the one in the header or the blocks. I tried this with box_grey, bluemarine, and a custom theme. Done lots of validation.
I'm really not sure how to go about resolving this problem.
Mike
Comment | File | Size | Author |
---|---|---|---|
#2 | search.module_6.patch | 412 bytes | markus_petrux |
Comments
Comment #1
mgiffordMight just be related to hitting return vs pressing submit
http://ppewww.ph.gla.ac.uk/%7Eflavell/www/formquestion.html
More testing to come..
Mike
Comment #2
markus_petrux CreditAttribution: markus_petrux commentedHi, I have also observed this problem with MSIE. Dumping the contents of the $_POST array relealed that the 'op' element (the submit button name) was not set, in my case. It looks like a bug in MSIE.
I have made a patch that seems to work, causing no side effects. Could you please check it out?
Comment #3
Steven CreditAttribution: Steven commentedCommitted to HEAD.
Comment #4
mgiffordthat patch worked great for me.. Thanks!
Comment #5
markus_petrux CreditAttribution: markus_petrux commentedSweet :-)
Although, for some reason MSIE was not sending the button, I haven't found any information about such an IE "behaviour".
The only related thing I found, which is what I first thought about, is that MSIE appends _x and _y with cursor coordinates for image buttons and sends them, instead of the button name itself. ie. if image button name is "mybutton", it sends "mybutton_x" and "mybutton_y".
Strange, really. Fortunatelly, this time, checking for the text field was enough.
Comment #6
(not verified) CreditAttribution: commented