Verified fixed in 1.3.1.
--
View this message in context:
http://www.nabble.com/DatePicker-NaN-tp12759906p15446234.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On Thu, 3 Jan 2008 21:29:18 +0100
"Gerolf Seitz" <[EMAIL PROTECTED]> wrote:
> Federico, is it possibly that you try it with the latest trunk?
> the fix is in and it will be included in 1.3.1
I'll try it ASAP, many thanks! :)
-
Federico, is it possibly that you try it with the latest trunk?
the fix is in and it will be included in 1.3.1
Regards,
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
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 alre
One way I work around this problem is to put the following on the textfield
for the date picker:
onfocus="this.blur();"
Doing that means the user can't simply type in the date, but you don't have
the NaN problem either.
On Jan 3, 2008 3:58 AM, Federico Fanton <[EMAIL PROTECTED]> wrote:
> On Wed
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 lo
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]>
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 ran into the
> another question eelco: what is the hidden input right after the
> .yui-container span for?
> iirc, it doesn't even have a name or id. see DatePicker#onRendered.
Don't remember that, and looking at it, it doesn't really make sense.
If you remove it and it still works, I'm fine with getting rid o
Eelco Hillenius wrote:
On 9/18/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
no, it's not intentional.
could you please file a bug report?
Yes please. What do we want here? The date picker not showing up in
the first place?
i'd say: have the datepicker clear the inco
On 9/18/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> Yes please. What do we want here? The date picker not showing up in
> the first place?
hm, maybe use the previously correct date?
another question eelco: what is the hidden input right after the
.yui-container span for?
iirc, it doesn't
On 9/18/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
> no, it's not intentional.
> could you please file a bug report?
Yes please. What do we want here? The date picker not showing up in
the first place?
Eelco
-
To unsubscribe, e
no, it's not intentional.
could you please file a bug report?
thanks...
gerolf
On 9/18/07, Ivana Cace <[EMAIL PROTECTED]> 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 c
13 matches
Mail list logo