in case you mean [0], that's going to be dealt with probably tomorrow ;) [0] https://issues.apache.org/jira/browse/WICKET-1595
On Fri, May 9, 2008 at 1:52 AM, Hoover, William <[EMAIL PROTECTED]> wrote: > 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" in line 227 > > 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. 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 just swithed from 1.3.2 to 1.3.3 and that resultet in a javascript > > error > > > "type mismatch" in line 227, > > > wich is this line in wicket-autocomplete.js: > > > > > > menu.style.zIndex=index=="auto"?index:Number(index)+1; > > > > > > Only in IE (6.0) - firefox works fine. > > > Does anyone else see this problem? > > > > > > Niels > > > > > > > -- > > View this message in context: > > http://www.nabble.com/AutoCompleteTextField-%22type-mismatch%22-in-lin > > e-227-tp16560166p17135623.html Sent from the Wicket - User mailing > > list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
