Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iPad 1 with iOS 5.1.1 refuses validation when a date field is used #571

Closed
danmiser opened this issue Dec 13, 2012 · 3 comments
Closed

iPad 1 with iOS 5.1.1 refuses validation when a date field is used #571

danmiser opened this issue Dec 13, 2012 · 3 comments

Comments

@danmiser
Copy link

I have a small, straight HTML sample available here:
http://www.routexcel.com/jqm

Run this on an iPad 1 with iOS 5.1.1 and press the submit button.
//expected: Continues on to page 2
//actual: Pops up the native datepicker again

I boiled it down to this: This works fine when I leave everything else the same and use jquery.validate 1.8, but it fails starting in 1.9 (and 1.10.0). So the breaking change occurred between 1.8 and 1.9.

If you need something else, please let me know. Thanks!

@danmiser
Copy link
Author

It looks like this is related to this issue:
#549

I used the work-around in that thread (updated to deal with ISO 8601 date format of yyyy-MM-dd) and things work better. Would be nice to have a bit more control over incoming date formats in the jquery.validation library.

@jzaefferer
Copy link
Collaborator

I agree that the built-in date method is terrible, since it relies on the inconsistent Date constructor. I've created a ticket to use Globalize for localized validation, #581. That should fix or avoid this problem.

@jzaefferer
Copy link
Collaborator

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually.

To the reporter (or anyone else interested in this issue): If you're affected by the same issue, consider opening a new issue, with a testpage that shows the issue. Even better, try to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants