Thanks for clearing that up, Igor. I was under the impression that was the 1.3.3 release. Will definitely give this a run as well and confirm before I file any reports.
Cheers, Michael -----Original Message----- From: Igor Vaynberg [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 11:25 AM To: users@wicket.apache.org Subject: Re: AutoCompleteTextField scrolls entire page before you submit a jira ticket make sure it is also broken in the wicket-1.3.x svn branch - which will be the 1.3.4 release - nothing really mystical about it. -igor On Mon, Jun 9, 2008 at 11:15 AM, Michael Mehrle <[EMAIL PROTECTED]> wrote: > I have not gone back to 1.3.2 yet - will give this a run in a few. If it > works with 1.3.2 I will open a JIRA ticket for 1.3.3. > > FYI, I don't seem the only one experiencing this - someone else posted > about this as he was able to replicate the problem with one of your > wicket demos. > > Michael > > -----Original Message----- > From: Eelco Hillenius [mailto:[EMAIL PROTECTED] > Sent: Monday, June 09, 2008 11:12 AM > To: users@wicket.apache.org > Subject: Re: AutoCompleteTextField scrolls entire page > > On Mon, Jun 9, 2008 at 10:58 AM, Michael Mehrle <[EMAIL PROTECTED]> > wrote: >> Marcus - I did NOT resolve it yet - not getting much help here except >> for talk about some mystical 1.3.4 release I can't get my hands on. It >> breaks with everything we wrote here involving AutoComplete - and all > of >> it was working fine with 1.3.2 as far as I remember. So, this puppy is >> broken and if someone can point me the right way I would love to help >> fix it. But at this point I don't know where to start - not exactly a >> huge JavaScript/CSS aficionado. > > If this used to work, but doesn't now, you should be able to track > down the differences between the two releases. The first thing you > could try is to get the exact source of the AC component of 1.3.2 (all > releases are tagged in our SVN repo) and see if that makes the > difference. If it does, a change in that component did, if not, > something larger (the ajax engine for instance) is in play. > > Could you also open a JIRA issue for it if you confirmed this is a bug? > > Eelco > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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]
