Closed valx76 closed 11 years ago
@valx76 can you please give a try the build on the dev
branch?
Great it works now when removing the whole date string :)
Btw, I think the input field should be disabled by default, cauz' if we remove the last number of the result date (for example), it will change the date to a bugged one too..
In my case, I fixed the problem with a disabled input and it works well !
oh right, got it
1/1/2013 -> backspace -> 1/1/0201
Very odd, but I think the input field is done this way to allow the user to input dates without having to use the calendar.
With the current implementation, however, this is impossible... I will take a look
Yes, that's strange.. Hope this helps.
I'm leaving this open. it will be automatically closed when the fix will be committed to master branch
Oh right, I didn't know about that (not a really git user yet ^^) !
no problem
I suspect this was caused by Pull Request #75. I think I saw this coming but couldn't remember the exact reason. I'll try to take a look at it today if I get time.
Fixed in commit a3c5377b4c
ok I need to revert my fix because now it's useless
Which, 7ee5fbbce530c? There's no need to revert that, it probably should be there anyway.
yes. I tried without it and it's fine .ok I will not remove it
If I'm deleting the content of the text input when a date is chosen, loose the focus of the input and give the focus again, a problem occurs.
First, it writes 'undefined' in the text field, and then, if we lose/get focus again, it will give a bugged date (0000-01-01).
My goal is to reset the field. I think, when we're deleting the input content, the field should be blank and not with "undefined" text inside..
EDIT: I'm using this code
Thanks