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
Well i think this might not be necessary. I was using an altField '@' (timestamp) and my custom preset ranges were parsing the date on the target timezone.
This proved wrong because jQuery datepicker works on local time only. For the story, while the timestamps on the original element value were generated ok, the calendar, when the local timezone was different from the target timezone, was selecting other dates..
I now use an altField: 'yy-mm-dd' and i parse the date on my target timezone only at the end, at the point i want to use the result.
A new option 'formatRangeForDisplay' would be helpful. Especially when displaying dates in diff timezone than local.
The text was updated successfully, but these errors were encountered: