-
Notifications
You must be signed in to change notification settings - Fork 730
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
Using : typeable="true" not expected behavior #636
Comments
I ran into similar issues with typable set to true. Only solution I see is to disable typable. |
Anyone found a fix for this? I am facing the same issue. |
No :( |
I don't have a solution either but some extra info to the problem.
I use a custom format function which can't be read by Date.parse, so when someone deselects the input field, the date disappears.
The problem also only seems to occur when the day part is higher than 12. |
Same issue here :( |
Same issue here too 👎 |
I have the same issue. I don't know if it's the case for everyone, but at least for you korsarNek, I can tell it's because there is somewhere in the logic of vuejs-datepicker something that doesn't take localisation into account when validating the date. Such that when you have a date like 12/12/2019, the date is interpreted as MM/dd/yyyy instead of dd/MM/yyyy With the example above it works, because 12 is a valid month, but if you try to enter 16/12/2019, the date will be invalid. This is truly a common problem of dates for non american people. (damned us dates) Edit: I have checked, and clearly Date.parse is responsible. EDIT 2: |
If using
: typeable="true"
on the component, when selecting a date that is after today's date, it doesn't successfully select it. After trying to select a date the input clears.An example:
Today's date: 2018-11-11
Selected date: 2018-11-12
Component's date is blank
Here is whats my component looks like:
<datepicker :typeable="true" v-model="page.due_at" id="due" input-class="op-custom-input" format="dd/MM/yy" :language="ptBR"></datepicker>
It would be awesome to get some help!
The text was updated successfully, but these errors were encountered: