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
the app is sent to the background (suspended) but NOT KILLED (either by the user or by the system)
the date changes (either in the real world, or using the Date and Time settings for faster testing)
the app is resumed from the task list
the existing datepicker is loaded into memory
$scope.today is still d1
So if the datepicker is opened, then d1 shows the "Today" styling and clicking on the "Today" button goes to d1.
Normally, you would handle this in the app by listening to the resume event and then refreshing the object. But $scope.today is not refreshed as part of openDatePicker and I don't see a way to access it from outside the module to refresh it.
The text was updated successfully, but these errors were encountered:
Consider the following scenario:
d1
d1
$scope.today
is stilld1
So if the datepicker is opened, then
d1
shows the "Today" styling and clicking on the "Today" button goes tod1
.Normally, you would handle this in the app by listening to the
resume
event and then refreshing the object. But$scope.today
is not refreshed as part ofopenDatePicker
and I don't see a way to access it from outside the module to refresh it.The text was updated successfully, but these errors were encountered: