Does this address the behavior in IE? With a multi select, clicking tab works to select a new item (as it does in most browsers) but click on your chosen item replaces the first selected item and leaves the stub.
So for a set of, say, (Apple, Orange, Banana, Pear), typing "App" will bring up the list and allow you to click producing Apple, If you then type "ora" it will bring up the list again but if you click on Orange it should produce Apple, Orange, but instead it give Orange, ora i.e. it doesn't replace your stub with the selected item but rather the first selected item. Would love to see this fixed one day - has anyone else come across the problem? On Sep 9, 4:31 pm, alexbodn.gro...@gmail.com wrote: > hello friends, > > i have done a few improvements to the autocomplete module, to fix problems > and improve functionality: > > added selectOnly option to autoselect a result if there's only one. this may > save you a click. > > moved the loading indicator to the left side, in case the field is rtl. > requires a small plugin i made, attached here. a css entry is being added to > this effect. the included css file has this, but as oposed to the main > autocomplete.css, colors are given as names. it's nice, but i'm open to > changes ;) . > > added substrings, and substringsSeparators. as oposed to multiple, which > deals with a list of elements separated by a fixed string, > substringSeparators is a string made of chars, that each and any of them > provide a separator between autocompletable strings. it supports editing a > program with a closed list of keywords, and operators and spaces as > separators. > > added extraFields, a list of names or ids (if prefixed with #) of other > fields to provide as fieldname=value params to the ajax query. in case names > are provided, they are expected to be inputs in the same form as the input > itself. more complex relationship may be found by adding suitable callbacks > to extraParams, which i'd only ask to receive the $input and the key name as > parameters. > > pasted joern's solution to the tickethttp://ui.jquery.com/bugs/ticket/3587, > to allow pressing of other key combinations while an autocompletable fields > has focus, and still keep autocompletion valid. > > though i can't yet be very specific, i found multiple autocompletion buggy, > and hope to devote some time to contribute to it's fix too. > > -- > alex > > jquery.autocomplete.js > 32KViewDownload > > jquery.direction.js > 1KViewDownload > > jquery.autocomplete.css > 1KViewDownload > > smime.p7s > < 1KViewDownload
