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
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
Problem
The problem appears to be that, with angular 1.3, the ngModel.$viewValue passes a string in ISO format instead of a date object as used to be the case in angular 1.2. UI-Bootstrap then attempts to parse the String as either a JSON Date or a timestamp but not as an ISO date format causing it to display the ISO date string instead of the properly formatted date. You can observe this by setting a breakpoint here
Fix
The date object is still available in ngModel.$modelValue though and the fix is as simple as swapping ngMode.$viewValue for ngModel.$modelValue in the line I referenced above:
var date = ngModel.$modelValue ? dateFilter(ngModel.$modelValue, dateFormat) : '';
The text was updated successfully, but these errors were encountered:
As the title suggests, datepicker-popup does not properly format the date after a modal change when ui-bootstrap is used with angular 1.3
Demonstration Plunkr
Problem
The problem appears to be that, with angular 1.3, the
ngModel.$viewValue
passes a string in ISO format instead of a date object as used to be the case in angular 1.2. UI-Bootstrap then attempts to parse the String as either a JSON Date or a timestamp but not as an ISO date format causing it to display the ISO date string instead of the properly formatted date. You can observe this by setting a breakpoint hereFix
The date object is still available in
ngModel.$modelValue
though and the fix is as simple as swappingngMode.$viewValue
forngModel.$modelValue
in the line I referenced above:The text was updated successfully, but these errors were encountered: