aedmonds wrote: > If you've had some difficulty using the Autocompleter included in the > wonderful interface package, I found some fixes for bugs I was experiencing. > These bugs were happening when the input field was within a form and you > arrow down to the selection and hit enter. The callback fired but after the > form had been submitted :(. These couple of steps will help fix that. > > First, there are two "protect" methods in the iautocompleter.js code. Delete > the "protect" method located on line 353. It is incomplete and will throw > errors if the first "protect" method on line 210 is removed instead of this > method. > > Second, on line 425 (or 411 if you deleted the second "protect" method), > where the "protect" method is bound to the keypress... > > "wait a sec... that's no 'protect'. All I see is > '.keypress(jQuery.iAuto.potect)'!" you might say to yourself. If you did, > congrats, you found the second error. If you didn't say that, don't worry. > Just add the "r" to "potect" and the Autocompleter works like a dream. > > Hopefully this is updated soon (I know Stefan made an update a couple of > days ago but nothing changed for the Autocompleter). > > If you have no idea what the "interface" package is, you can go to > http://interface.eyecon.ro/ http://interface.eyecon.ro/ . > > As always, thanks John for jQuery, and thanks Stefan for interface. > > -Aaron > Wow, nice, it is like a solution for a RPG, but I don't like to play computer games.
Long story short: the protect function was duplicated, delete one and correct typo. I will update today. _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
