Ah, also set minChars: 0, that way a double click on the field
displays the list of values.
Jörn
On Tue, Jun 24, 2008 at 11:09 AM, Jörn Zaefferer
<[EMAIL PROTECTED]> wrote:
> Yes, a progressive enhancement from a select to an autocomplete is
> definitely planned. Its not hard to do anyway: Create a text input,
> append it before or after the select, hide the select, initialize the
> input with autocomplete and pass the options as the autocomplete data.
> Add a button image that indicates the field being equivalent to a
> select.
>
> Something like this:
> $("select").each(function() {
> var data = $(this).hide().find("option").map(function() {
> return $(this).text();
> });
> $("<input/>").insertAfter(this).autocomplete(data, {mustMatch: true});
> });
>
> Jörn
>
> On Tue, Jun 24, 2008 at 10:50 AM, Enrique Meléndez Estrada
> <[EMAIL PROTECTED]> wrote:
>>
>> hi Jörn,
>> I see that your great plugin, autocomplete, can also behave like a combobox
>> (a subset of...), in the sense that the result must match one of the
>> possible values (practically, identical to a <select><options> html tags),
>> correct me if I'm wrong.
>>
>> So, It would be veeeeery interesting to have, not only input and textarea,
>> but selects, as well, autocompleteable, and in this last option, to have
>> default behaviour of a combobox (must match, contains, local (obviously),
>> etc...). All to be more "accessible": if no autocomplete/combobox plugin,
>> you find your normal SELECT. And also, without the need of a special format
>> for the data (the data is the proper <option> tags).
>>
>> is this in your plans for a next release? does this make any sense to you?
>> perhaps a "converter" from select/option to input/your data format in order
>> to use the autocomplete? (this last case is very expensive if you have
>> thousands of options...)
>>
>> thanx a lot,
>>
>> --
>> Enrique Meléndez Estrada (2367)
>> Servicios Informáticos
>> Organización y Servicios Internos
>> Instituto Tecnológico de Aragón
>>
>>
>
