jira, patch, etc... the mailing list is not a good place to report bugs.
-igor
On Wed, Oct 29, 2008 at 7:40 AM, Shailesh Verma <[EMAIL PROTECTED]> wrote:
>
> I am using wicket-extensions v 1.3.5 and see the javascript "Type Mismatch"
> error on Line 287 of wicket-autocomplete.js. This error comes
I am using wicket-extensions v 1.3.5 and see the javascript "Type Mismatch"
error on Line 287 of wicket-autocomplete.js. This error comes on IE6.0 only.
Firefox works ok.
Shailesh
Gerolf Seitz wrote:
>
> it's fixed in the upcoming 1.3.4 and the already release 1.4-M1
>
> Gerolf
>
> On Thu
TECTED]
> Sent: Thursday, May 08, 2008 7:57 PM
> To: users@wicket.apache.org
> Subject: Re: AutoCompleteTextField "type mismatch" in line 227
>
> in case you mean [0], that's going to be dealt with probably tomorrow ;)
>
> [0] https://issues.apache.org/jira/brow
that is it :o)
i'm assuming the same issue also causes the selection to be lost on
occasion
-Original Message-
From: Gerolf Seitz [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 08, 2008 7:57 PM
To: users@wicket.apache.org
Subject: Re: AutoCompleteTextField "type mismatch"
oard events combo ;o)
>
> -Original Message-
> From: Gerolf Seitz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 08, 2008 4:23 PM
> To: users@wicket.apache.org
> Subject: Re: AutoCompleteTextField "type mismatch" in line 227
>
> it's fixed in the u
Although, it still has some issues when dealing with mouseover and
keyboard events combo ;o)
-Original Message-
From: Gerolf Seitz [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 08, 2008 4:23 PM
To: users@wicket.apache.org
Subject: Re: AutoCompleteTextField "type mismatch" i
it's fixed in the upcoming 1.3.4 and the already release 1.4-M1
Gerolf
On Thu, May 8, 2008 at 10:20 PM, taygolf <[EMAIL PROTECTED]> wrote:
>
> Yes I am just starting to try and get the autocompletetextfield working on
> my
> app and I am using wicket 1.3. as well and it is doing the same thing
Yes I am just starting to try and get the autocompletetextfield working on my
app and I am using wicket 1.3. as well and it is doing the same thing. It is
throwing a js type mismatch error. Works fine in firefox but not in IE.
Did you figure out the problem?
T
Niels Bo wrote:
>
> Hi
>
> I ju
