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
I have a calendar which utilizes the disable_dates & enable_dates features to only allow choosing certain days within a month. I am also using the direction to ensure no dates in the future can be selected.
Today is December 1st, and that particular day is not within the enabled dates, thus December has no available dates (the most recent available in this case is Nov 15th). However, when I open the picker into months view (my default initial view) it allows choosing Dec. Then if I do choose December I am brought into days view with all of the days disabled.
This is confusing to my end users, who would expect the Dec option to be disabled in the months view.
I presume a similar issue will happen in about a month where, come Jan 1st 2017, not only will Jan be enabled in months view, but 2017 will be enabled in years view despite no dates being available in 2017 yet at that point.
The text was updated successfully, but these errors were encountered:
I have a calendar which utilizes the disable_dates & enable_dates features to only allow choosing certain days within a month. I am also using the direction to ensure no dates in the future can be selected.
Today is December 1st, and that particular day is not within the enabled dates, thus December has no available dates (the most recent available in this case is Nov 15th). However, when I open the picker into months view (my default initial view) it allows choosing Dec. Then if I do choose December I am brought into days view with all of the days disabled.
This is confusing to my end users, who would expect the Dec option to be disabled in the months view.
I presume a similar issue will happen in about a month where, come Jan 1st 2017, not only will Jan be enabled in months view, but 2017 will be enabled in years view despite no dates being available in 2017 yet at that point.
The text was updated successfully, but these errors were encountered: