You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a max="2002-08-03" gets added which conflicts with the date format I specify for Flatpickr. Seems like I will have to use something like moment.js to validate dates.
Edit:
Looking further into the issue, it seems Parsley is not comparing the dates properly. If I simply add max="2002-08-03" then the validation passes even if I enter a date beyond the maximum.
What kind of issue is this? (put 'x' between the square brackets)
Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use
http://stackoverflow.com/questions/ask .
Provide working code, starting from http://codepen.io/marcandre/pen/jqbzyN?editors=101.
We monitor the tag
parsley.js
.[ x] Bug report. If you’ve found a bug, you must provide a minimal example in a CodePen,
starting from http://codepen.io/marcandre/pen/jqbzyN?editors=101 .
Feature Request. Make sure there's no good way to do what you want first;
consider asking on http://stackoverflow.com/questions/ask first.
Hello,
I am using Flatpickr as my date UI. Everything is working fine on a desktop application, however, when I test my site on a mobile browser I get a bug.
Steps
<input class="input datepicker-dob" placeholder="Select Date" type="text" name="dateOfBirth" data-parsley-date data-parsley-validate-if-empty data-parsley-required="true">
"datepicker-dob" is simply the class to which Flatpickr attaches. I get the below error even if I remove the data-parsley-* attributes.
Flatpickr is set up as below:
This error goes away when I request the mobile site, so I am not sure what is going on here.
I have recreated this issue on safari, and chrome, both on an iphone device.
Any ideas on what could cause this issue?
Thanks
The text was updated successfully, but these errors were encountered: