Hi Thomas, the prototype Element.observe function changes keypress observing to keydown observing on Safari, i think because of the strange keyCodes delivered by keypress events in Safari. Safari cancels submission on keypress events, but not on keydown events.
Regards, Lorenz On 01.09.2006, at 19:11, Thomas Fuchs wrote: > > Works on Safari 2, but it also submits the form (iirc, that's > something > we tried fixing on Safari, but somehow it didn't work out). > > -Thomas > > Am 01.09.2006 um 11:57 schrieb Christophe Porteneuve: > >> >> Hi, >> >> Actually Firefox' behavior is the correct one. >> >> You will, however, find a similar issue on Opera9, which is my >> problem >> just now. >> >> When there's no positioned container to the text input, it will >> display >> the completions at (0,0) of the body (+ body margins). >> >> If there is a positioned container, it will display at proper top >> offset, but still at zero left offset. >> >> I put a reproducible case online: >> http://www.tddsworld.com/bugs/autocompleter_opera9_issue/index.html >> >> It doesn't use any positioned container. This very page works fine on >> MSIE 6, Firefox 1.5 and Konqueror 3.5.2. I haven't got Safari >> feedback >> yet. >> >> Position.clone, which is Prototype stuff, does seem to be the culprit >> here, but I need a solution quick. Those willing to tinker with this >> code can find a ZIP file on the online demo's parent directory. >> >> Thanks in advance all, >> >> -- >> Christophe Porteneuve >> >> >>> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
