As long as we are picking on DateField I created this issue: https://issues.apache.org/jira/browse/TAP5-2173
The problem is the combination of DateField and the conversion of Strings to SimpleDateFormat allow dates such as 2013-09-67 to be considered valid and that input returns Wed Nov 06 00:00:00 CST 2013. If you read the documentation this behavior is to be expected but I don't think it's the correct default behavior and is at best a usability problem. Since I don't think most people would enter 2013-09-67 and expect 2013-11-06 the worse case is end up with unreliable data in your database with no errors and no way to differentiate the good input from the bad. I was not able to completely work around this problem without creating my own DateField component. On Thu, Sep 5, 2013 at 10:35 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > Now since my bootstrap issues are cleared up, the state of the datepicker > is still leaves something to be desired. > This is actually the same state it was since T5.3, with the following bugs > still not fixed: > > https://issues.apache.org/jira/browse/TAP5-805 > Take a look at my last comment. Basically, currently, a user types in > gibberish in the date field, the date picker will not longer pop up, > which is a usability issue. > > https://issues.apache.org/jira/browse/TAP5-1845 (obsolete colors, causing > issues on some systems) > > https://issues.apache.org/jira/browse/TAP5-1408 > This should be re-opened. Users are required to click on the little > calendar button in order to cancel the datepicker. > This isn't good usability-wise. They should be able to click anywhere on > the page > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
