We are using the jQuery UI date picker. Just checked now - it does prevent alpha characters from being entered, but not prevent invalid dates from being entered by hand, e.g. 123/45/67.
We also had a client who requested an application to function without JS enabled. It was not practical in that particular case, but I can see that these scenarios do come up. -----Original Message----- From: cfcdev@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Barry Beattie Sent: Tuesday, 14 October 2008 6:21 PM To: cfcdev@googlegroups.com Subject: [CFCDEV] Re: Using object "getters" after form validation fails you've never come across former terminal/green screen users, then. data entry operators who can fly through dozens of form elements using taborder, <enter> and shortcut keys to do so. you want horror stories of 50-70 form fields on one screen, micro-business logic modifying the taborder and/or disabling form elements and/or kicking in custom validation? where entering "12102008" in a text box will automatically render it as "12/10/2008" as a date in October? thank small miracles for CF custom tags as tag libs to reuse controls. Pity it all happened pre Flex2. On Tue, Oct 14, 2008 at 4:51 PM, Mark Mandel <[EMAIL PROTECTED]> wrote: > > 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 -~----------~----~----~----~------~----~------~--~---
