This question is locked. New answers and comments are not allowed.
I found a little bug in DatePicker behaviour when selecting a date using a mouse scrollwheel. This appears to be happening when a MinDate or MaxDate has been specified. It can be reproduced by using the sample I already provided in this post but a single DatePicker will probably show the same behaviour.
To reproduce take the linked sample or a new datepicker. When running the app the right datepicker is set to a MinDate of today and MaxDate today + 30, current value is today +1. So when changing just the day only 19 - 31 sept are allowed, 1-18 are not.
If I select a new day using touch/mouseclick this works, since clicking disabled dates doesn't work. Now if I hover above the day I can select a new date by scrolling the scrollwheel. This works when I stay within the allowed range. If I scroll any further the UI stays on the Min or Max date (that's expected behaviour), but when accepting this date a new date is NOT set. This is probably a little bug that has to do with the way the Max and Min date are handled, could somebody look into this?
So basically the problem is that when (accidentally) scrolling over the Max or Min date the UI correctly prevents scrolling any further, but accepting the new date doesn't work anymore.
To reproduce take the linked sample or a new datepicker. When running the app the right datepicker is set to a MinDate of today and MaxDate today + 30, current value is today +1. So when changing just the day only 19 - 31 sept are allowed, 1-18 are not.
If I select a new day using touch/mouseclick this works, since clicking disabled dates doesn't work. Now if I hover above the day I can select a new date by scrolling the scrollwheel. This works when I stay within the allowed range. If I scroll any further the UI stays on the Min or Max date (that's expected behaviour), but when accepting this date a new date is NOT set. This is probably a little bug that has to do with the way the Max and Min date are handled, could somebody look into this?
So basically the problem is that when (accidentally) scrolling over the Max or Min date the UI correctly prevents scrolling any further, but accepting the new date doesn't work anymore.
1 Answer, 1 is accepted
0
Accepted
Hi Tom,
Thank you for contacting us and for your feedback.
I was able to reproduce the bug on my side and I have fixed it in our codebase. We believe that it is a minor bug that does not affect an app critically, so we will ship the fix with the official release, expected somewhere by mid-October. Please let us know whether this fits your schedule or you need a fix earlier.
Once again - thanks for your detailed and valuable feedback - it really helps us build better components. I have updated your Telerik points as a token of our gratitude. Do not hesitate to write us back with any question/problem you may have with our tools.
Kind regards,
Georgi
the Telerik team
Thank you for contacting us and for your feedback.
I was able to reproduce the bug on my side and I have fixed it in our codebase. We believe that it is a minor bug that does not affect an app critically, so we will ship the fix with the official release, expected somewhere by mid-October. Please let us know whether this fits your schedule or you need a fix earlier.
Once again - thanks for your detailed and valuable feedback - it really helps us build better components. I have updated your Telerik points as a token of our gratitude. Do not hesitate to write us back with any question/problem you may have with our tools.
Kind regards,
Georgi
the Telerik team
Time to cast your vote for Telerik! Tell DevPro Connections and Windows IT Pro why Telerik is your choice. Telerik is nominated in a total of 25 categories.