Search and Top Navigation
#14918 closed bug (duplicate)
Opened February 13, 2016 01:26AM UTC
Closed February 15, 2016 03:38PM UTC
Date format "M yy" causes output date to always be "now"
| Reported by: | colemanw | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | ui.datepicker | Version: | 1.11.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
As the title says, the datepicker appears to work, but actually has no idea what date was just selected:
http://jsbin.com/fazasusupu/edit?js,output
I guess a broken clock is right twice a day...
Attachments (0)
Change History (3)
Changed February 13, 2016 01:35AM UTC by comment:1
Changed February 13, 2016 12:07PM UTC by comment:2
| _comment0: | Seems to be related to the month selection... Just tested http://jsbin.com/fazasusupu/edit?js,output and found that if the selected month is the same as the month currently entered, then it will save the new date value correctly. \ \ However if you change the month (e.g. go back one month), then click a day, the value defaults to now. Repeat this process (selecting the same month again) the date will then be updated correctly. \ \ Hope this helps. → 1455365301943127 |
|---|
Doh! Just seen your comments, colemanw! :)
Note that you need to change the month in the datepicker to trigger the bug. For some reason the current month works correctly.