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
When a Moment object is used for ng-model instead of a Date object, the timezone information set on the moment is lost.
The code is using a moment's underlying Date object which doesn't contain any timezone information.
If supporting moment.js, I think it is important to retain timezone information or at least call out in the documentation that timezone information will be lost.
I think that for now we won't support moment.js with timezone information (unless someone writes a pull request: we're up for that). Ideally I'd like jquery-timepicker to support moment.js (with timezones), so that this codebase only serves as a thin wrapper between the timepicker and Angular
When a Moment object is used for ng-model instead of a Date object, the timezone information set on the moment is lost.
The code is using a moment's underlying Date object which doesn't contain any timezone information.
If supporting moment.js, I think it is important to retain timezone information or at least call out in the documentation that timezone information will be lost.
http://plnkr.co/edit/BqBS59XvZlH5KMbulTgQ?p=preview
The text was updated successfully, but these errors were encountered: