Both problems should now be fixed on IE 6.

regards
musachy

Musachy Barroso wrote:
> I will fix it so it ignores that null value. UTF-8 works.
>
> regards
> musachy
>
> Dariusz Wojtas wrote:
>> I am not really sure if it worked before, both autcompleter and my
>> code do evolve ;)
>> I was always using JSP with UTF-8 encoding to generate my options.
>> Is UTF-8 a problem here?
>>
>> You mean
>>   [ ["A", "B"] , ]
>> is problematical for IE, but
>>   [ ["A", "B"] ]
>> will work? Should I change something in the json list generation or
>> the autocompleter will recognize such case?
>>
>> Dariusz Wojtas
>>
>> On 12/28/06, Musachy Barroso <mbarroso@(protected):
>>> This is what I found so far, there are 2 problems, one is that when
>>> there is a json array like:
>>>
>>> [ ["A", "B"] , ]
>>>
>>> IE puts a null object in the array. That one is easy to fix. The other
>>> problem is that using freemaker, like in showcase to render the json
>>> array, the charset of the response is set to Cp1252, which causes the
>>> error on IE. If I use a jsp to render the json array, the encoding is
>>> ISO-8859-1 which works fine. Was this working for you before?
>>>
>>> regards
>>> musachy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@(protected)
>> For additional commands, e-mail: user-help@(protected)
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)