I filed a bug a few days ago. 

On 2/23/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
have you filed it so that we know that its there?

-Igor


On 2/23/06, Frank Silbermann < [EMAIL PROTECTED] > wrote:

I've done some further testing on the DatePicker popping up when running the FormInput example, and here are the results:

 

wicket-examples-1.1.1                works in both InternetExplorer and Mozilla

wicket-examples-1.2-20060221   works in Mozilla, but not InternetExplorer

 

So the DatePicker's inability to work with InternetExplorer is a bug introduced in the new version under development.  I don't think my employer would accept a requirement for users to go to Mozilla, but I need the features of Wicket 1.2 -- so I hope this bug is fixed soon.

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Nick Heudecker
Sent: Monday, February 20, 2006 10:12 PM
To: [email protected]
Subject: Re: [Wicket-user] DatePicker won't pop up

 

I don't know what JAR versions the Forminput example is using.  I've updated the priority from 5 to 7. Here's the bug:
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1434895&group_id=119783

I tried loading each of the resources the DatePicker adds to wicket:head and that worked fine.  The _javascript_ added to the page, next to the text field, is what seems to be causing the problem. 

Another question is if the underlying date picker _javascript_ code has changed.

On 2/20/06, Frank Silbermann < [EMAIL PROTECTED] > wrote:

I've just noticed that it works for me in Mozilla.

 

But why, then, does the FormInput example's DatePicker work for me in IE?  Is there some configuration or property file setting needed to make it work in IE?  Some Cascading stylesheet setting required?

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Nick Heudecker
Sent: Monday, February 20, 2006 11:59 AM
To: [email protected]
Subject: Re: [Wicket-user] DatePicker won't pop up

 

I'm having this problem on IE, but it works fine on FF.  I've opened a bug on this issue.

 



Reply via email to