11 Answers, 1 is accepted
I was not able to reproduce the behavior in a sample from my end. Please have a look at it and provide more information on when exactly the issue appears so we can investigate it.
Have a great rest of the week.
Regards,
Stefan Nenchev
Progress Telerik
Thank you for the update.
It seems that the issue is reproducible in iOS. I have logged it as a bug report at our end. Here is the public item which you can follow in order to receive automatic notifications - Calendar: [iOS]Not able to navigate to the month that contains the MaxDate. Once again, I have added some points to your account for reporting the behavior.
Regards,
Stefan Nenchev
Progress Telerik
Is there any plan for this bug, being fixed in near future - https://feedback.telerik.com/Project/168/Feedback/Details/237335-calendar-ios-not-able-to-navigate-to-the-month-that-contains-the-maxdate
The only "workaround" that I've found, is to:
-when we have would like to set Max Date to *11/27/2017 12:00:00 AM* (12AM, so midnight)
-we should set *SelectedDate* to exact this date - *11/27/2017 12:00:00 AM* (12AM, so midnight)
-set *MaxDate* to "bigger" date - i.e. *11/27/2017 1:00:00 AM* (1AM, so hour after midnight)
After that we are able to see correct *SelectedDate*.
Issue occurs only on iOS - on Android it's working fine to set EXACT the same DateTime value for SelectedDate and MaxDate - in. *11/27/2017* - we are able to set this day in Calendar picker, and this is the greatest day that could be selected (we are not able to select 11/28/2017, which is correct).
This could be related to DateTimeKind, but most likely at Telerik side, as in whole app, I'm using UTC + there is no issue on Android.
It's seems to be 99% DateTimeKind issue on Telerik side, as setting MaxDate = 11/27/2017 12:59:59 AM didn't allows to set SelectedDate to 11/27/2017 12:00:00 AM.
Similarly setting MaxDate = 11/27/2017 11:00:01 PM allows to set also 11/28/2017 as selected date.
So the way to allow really setting MaxDate in UI to given DAY is to set MaxDate between <givenMonth>/<givenDay>/<givenYear> 1:00:00 AM till <givenMonth>/<givenDay>/<givenYear> 10:59:59 PM.
Thank you for sharing the workaround and the result of your research.
This issue is logged with high priority in our backlog and hopefully we will be able to include it in the upcoming release.
I am sorry for any inconvenience caused.
Regards,
Yana
Progress Telerik
Are there any points for bug reporting / workaround delivering :D?
Usually telerik points are granted for newly discovered issues. However, since you've researched in details the reasons behind the erroneous behavior, I've added some points to your account.
Let me know if I can assist with anything else.
Regards,
Yana
Progress Telerik
Any update on that - you says it's *high priority*, but here - https://feedback.telerik.com/Project/168/Feedback/Details/237335-calendar-ios-not-able-to-navigate-to-the-month-that-contains-the-maxdate - I see it's still *Approved* and unfortunately *Not Scheduled*?
I confirm the issue is with high priority in our backlog, however, some of our top priority issues for the release were delayed due to more urgent tasks. The team is currently working on the mentioned issue and as soon as there is some progress on it, we'll update the status of the feedback item.
I am sorry for any inconvenience caused.
Regards,
Yana
Progress Telerik