[
https://issues.apache.org/struts/browse/WW-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Szőts reassigned WW-3211:
--------------------------------
Assignee: Craig McClanahan
Since this bug has remained untouched for a while, I decided to randomly assign
it, sorry.
In my own build this issue is solved, but as a beginner I wouldn't dare to try
anything even with commit rights.
As our client requested, we handle invalid input by setting the current date in
our version.
> Struts:Datepicker issues
> ------------------------
>
> Key: WW-3211
> URL: https://issues.apache.org/struts/browse/WW-3211
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Dojo Tags
> Affects Versions: 2.1.6
> Reporter: Viktor Szőts
> Assignee: Craig McClanahan
> Priority: Minor
>
> After erasing the content of a Struts:Datepicker, the dateselector fills up
> with "NAN"s and "undefined"s. After paging upwards , it jumps to the maximum
> date.
> If invalid date is typed in the datepicker's inputNode, it jumps to January
> 1, 1970, 00:00:00.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
