Finally a ticket: http://ui.jquery.com/bugs/ticket/3587
Jörn On Mon, Oct 20, 2008 at 2:59 AM, alex bodnaru <[EMAIL PROTECTED]> wrote: > backspace support added. > alex > > On Mon, Oct 20, 2008 at 02:08, alex bodnaru <[EMAIL PROTECTED]> wrote: >> don't tell me i forgot to attach the file ;) >> >> On Sun, Oct 19, 2008 at 18:15, alex bodnaru <[EMAIL PROTECTED]> wrote: >>> hello dan, everybody. >>> >>> i have posted yesterday on this list a few improvements to >>> autocomplete for your review, >>> which i'd be glad to see committed if ok. >>> >>> as it turned out, the work was more delicate, but with your expert >>> guidance i got the >>> hoped result. >>> >>> here is jquery.autocomplete.js, as patched to ignore noisy key presses >>> and to additionally >>> append fields values to the ajax query. >>> >>> last but not least, i have given the input widget focus after >>> selection from the list, since >>> this widget is made for people who wish to use the keyboard. >>> additionally, maybe a configuration >>> option will allow automatic move to the next field, to save even more >>> fuss from the user. >>> >>> please take a look an freely use my work. >>> >>> best regards, >>> alex >>> >>> On Sun, Oct 19, 2008 at 17:40, alex bodnaru <[EMAIL PROTECTED]> wrote: >>>> hi dan, >>>> >>>> thanks for your answer. >>>> >>>> i'm logging the keydown event on the input in the plugin autocomplete. >>>> >>>> the keydown is there to react to movement, return and delete, and in >>>> the default condition it >>>> may check for eventual changes in the input field. >>>> >>>> but, pressing of a hebrew character immediately after the keymap >>>> switching with alt-shift >>>> (which is itself captured by keydown as alt) is not getting in keydown >>>> at all, however it >>>> changed the field value. >>>> anyway, the keyCode of hebrew chars in keydown is always 0. >>>> >>>> i will try to move handling of non movement keypresses in keypress, >>>> and soon report. >>>> >>>> best regards, >>>> alex >>>> >>>> On Sun, Oct 19, 2008 at 15:47, Dan Switzer <[EMAIL PROTECTED]> wrote: >>>>> Alex, >>>>> >>>>> What keyboard event are you logging? Some events are only captured by a >>>>> keypress event and will be ignored by the keydown event. >>>>> >>>>> -Dan >>>>> >>>>> On Sun, Oct 19, 2008 at 5:12 AM, alex bodnaru <[EMAIL PROTECTED]> >>>>> wrote: >>>>>> >>>>>> hello friends, >>>>>> >>>>>> i ran into a corner case with jquery autocomplete which i'd like to >>>>>> seek a solution for: >>>>>> >>>>>> my system is bilingual (en-he) gnome debian linux, with firefox 3.0.3. >>>>>> >>>>>> with focus on an autocomplete field, i'm switching the keymap to >>>>>> hebrew, using alt-shift. logging the event keyCode to the firebug >>>>>> console, i get one 18 value, followed sometimes by a 0 additional >>>>>> event. >>>>>> >>>>>> the next character i'm typing into the field is being shown, but does >>>>>> not trigger a keycode event, hence the autocompletion doesn't react. >>>>>> this doesn't happen when i switch the language to english, probably >>>>>> because ascii characters have non-zero keyCodes. >>>>>> >>>>>> but the following character i'm typing acts ok. no, this is not >>>>>> because minChars. >>>>>> >>>>>> i assume that the alt-shift is leaving the event manager in an >>>>>> ambiguous state, which invalidates an unicode char, but is being later >>>>>> cleaned by typing another char, or bksp/del. >>>>>> >>>>>> could you help? >>>>>> >>>>>> best regards, >>>>>> alex >>>>> >>>>> >>>> >>> >> >
