> 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? >>
Perfect solution, but that was just one example of not repopulating a field that fails the property type set. @Jean - good point - but not big enough of an issue for me to worry about now. Maybe as I flush out my process I will find a solution for it. But still, if I prompt them for age and they enter aa, and enter aa again, and they have JS turned off, I am OK with passing on that user. Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
