what's wrong with having a date picker? On 10/14/08, Jean Moniatte <[EMAIL PROTECTED]> wrote: > I disagree. > > Whatever solution we decide to implement (server or client) should never > affect the user experience, and data that does not validate should always be > displayed in its original field. In the context of your example, a European > user might very well enter 31/12/2008 as a date. That would not be clueless. > > Jean > > What if a European user enters 31/12/2008 for a date? > > On Mon, Oct 13, 2008 at 5:35 AM, Dan O'Keefe <[EMAIL PROTECTED]> wrote: > >> >> > As far as I'm concerned, if the user disables JavaScript and enters >> > "aaa" >> > into a date field, it's just too bad that the redisplayed form doesn't >> show >> > "aaa" in that date field. The validation error message tells them about >> the >> > problem, and to me having "aaa" show up in the form again is just an >> > invitation for the user to submit the bad data again. >> > >> >> >> Could not agree more. I am all for usability but at some point, have >> to put some ownership on the user to have a clue. Thanks for the >> verification. I am going to model out a test case and try it. >> >> Dan >> >> > >> > > > >
-- E: [EMAIL PROTECTED] W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to cfcdev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
