Thanks for helping out on the mailing list in my absence. I was
actually in your country for three hours on Sept. 16 (at Heathrow).
I'm not sure how to respond to your question. I had never planned on
having to write a lot of JS to support VT, which is why I relied on
the jQuery plugin so much. I suppose we have now changed things so
that we are mostly writing our own JS for the majority of types, but I
don't think we want to go crazy trying to address edge cases. If this
is simply an issue of the client-side code not being set up to support
certain date formats then I think that as long as we support the most
common ones we shouldn't worry about it.
Bob
> --
> You received this message because you are subscribed to the Google Groups "ValidateThis-dev" group.
> To post to this group, send email to validate...@googlegroups.com.
> To unsubscribe from this group, send email to validatethis-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/validatethis-dev?hl=en.
>
>
--
Bob Silverberg
www.silverwareconsulting.com
I saw you were in Italy - looked nice :) Obviously for sheer beauty
and glamour, then Heathrow is hard to beat!!
I'll stop worrying about US, UK, German date formats then on the client side :)
I've pushed to my qunit branch. I wouldn't mind you having a look. You
can run the qunit tests by calling:
http://localhost/validatethis/tests/qunit/clientsidevalidators.cfm
I've tested against IE9, Safari 5, Chrome 14 and Firefox 6 on Windows
7. I've run the selenium tests and they are all passing so would be
good to test on a Mac as well in case the browser(s) behave
differently.