Alright, it seems that the 1.3-SNAPSHOT release fixes the scrolling
problem. HOWEVER, in IE I still experience a strange z-depth problem.
Meaning that the drop down menu appears *behind* neighboring form fields
- take a look at this screenshot:

http://screencast.com/t/DsqIA4pxtut

Any thoughts? I'm going to post this in its own thread to make sure a
few more folks look at this.

Thanks,

Michael


-----Original Message-----
From: Igor Vaynberg [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 09, 2008 1:40 PM
To: users@wicket.apache.org
Subject: Re: AutoCompleteTextField scrolls entire page

svn co https://svn.apache.org/repos/asf/wicket/branches/wicket-1.3.x
wicket-1.3.x
cd wicket-1.3.x
mvn install

-igor

On Mon, Jun 9, 2008 at 1:18 PM, Michael Mehrle <[EMAIL PROTECTED]>
wrote:
> Igor - please help me out - I have been trying to download that
snapshot
> branch/tag but it keeps failing. I'm using maven and am following the
> instructions (http://tinyurl.com/5dnxsf), but it keeps failing.
>
> 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]
>
>

---------------------------------------------------------------------
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]

Reply via email to