i reopened the issue and will take a look at it tonight. thanks for reporting it.
Gerolf On Jan 3, 2008 10:58 AM, Federico Fanton <[EMAIL PROTECTED]> wrote: > On Wed, 19 Sep 2007 18:19:15 +0200 > "Gerolf Seitz" <[EMAIL PROTECTED]> wrote: > > > ivana filed an issue today (WICKET-989) and i already attached a patch > to > > it. > > so either you persuade any of the committers to apply the patch and > commit > > it, or you do an svn checkout and apply the patch to your local copy of > > wicket-datetime. > > > > Gerolf > > > > On 9/19/07, Philip Köster <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > ivana wrote: > > > > > > > > Hi > > > > I have a problem with the DatePicker. It works fine if the input is > a > > > > valid date or if the input is very wrong, for example: ''xxx". > > > > But when the input consists of numbers and but is not a valid date, > the > > > > calendar is rendered with NaN in every field. > > > > I'm sorry, could it be that somehow this patch wasn't included in 1.3.0? I > upgraded today and I'm still having the same problem.. If I write "123" in > the text box and I press the calendar icon, the datepicker is full of NaNs. > I checked wicket-date.js and it looks like it doesn't check for NaNs.. > Thanks for your time! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
