Okay, thanks for the clarification. Though I still can't reproduce the
problem your describe - the autocomplete iterates over the data array
with an index-based for loop, and anything added to the array
prototype is ignored.
Can you provide a testpage where the issue actually occurs in
One more thing: I'm using the autocomplete on a project where Ext is
also installed, and there are no compability issues.
Jörn
On Wed, Jul 2, 2008 at 10:24 AM, Jörn Zaefferer
[EMAIL PROTECTED] wrote:
Okay, thanks for the clarification. Though I still can't reproduce the
problem your describe
Hi Jörn,
The problem in fact is Ext Related, yet can be reproduced without Ext:
any library that expands the Array prototype with a function can be
the wrongdoer.
Create a new blank document (nothing needs to be in it), open up
firebug and paste in the code below:
Okay, so the issue is that letsBreakStuff gets iterated together with
the rest of the array, while it should be ignored, as it doesn't have
a numerical index, right?
How does that relate to your patch?
Jörn
On Tue, Jul 1, 2008 at 11:36 AM, Bramus! [EMAIL PROTECTED] wrote:
Hi Jörn,
The
Hi Jörn,
exactly, the function gets iterated too and is considered as the last
element of the array. When passed on to autocomplete, it will break as
s.toLowerCase() is invalid when s isn't a string. Therefore; my patch
over at
Filed a ticket on dev.jquery including a .diff file:
http://dev.jquery.com/ticket/3080
;-)
Regards,
B!
PS: [autocomplete] prefix seems to be cut off subject?
On Jun 24, 11:15 am, Bramus! [EMAIL PROTECTED] wrote:
Hi Jörn et all here at the list,
I'm using the autocomplete plugin in a
I don't quite the how the issue is related to ExtJS. It sounds like
you pass functions instead of strings to the autocomplete plugin,
which is the actual issue here. Could you upload a testpage and post
the URL here?
Jörn
On Tue, Jun 24, 2008 at 1:03 PM, Bramus! [EMAIL PROTECTED] wrote:
Filed
7 matches
Mail list logo