I'm using Tempus Dominus Bootstrap 4, version 5.0.1 in my ASP.Net application (VS 2017, .Net framework 4.7) along with Bootstrap version 4.5.0.
In my Payment page, while initialising the DateTimePicker in the aspx section, I'm setting the minDate and maxDate options. I'm also setting the format to 'DD/MM/YYYY hh:mm A'. While running the page, when I pop up the calendar control of the DateTimePicker and try to select any date beyond the minDate and maxDate range using the mouse, the control correctly disables the selection and stops me from selecting any invalid date. However, if I write any invalid date beyond the range by using keyboard, the control isn't validating it, therefore allowing invalid date to pass to the server-side. How do I stop it from doing so?
I'm using the updated versions of moment.js and FontAwesome. I've also tried using min and full versions of Tempus Dominus, moment and FontAwesome separately, yet it's showing date beyond the range of minDate and maxDate. Am I missing something or is it an inherent issue?
I'm using Tempus Dominus Bootstrap 4, version 5.0.1 in my ASP.Net application (VS 2017, .Net framework 4.7) along with Bootstrap version 4.5.0.
In my Payment page, while initialising the DateTimePicker in the aspx section, I'm setting the minDate and maxDate options. I'm also setting the format to 'DD/MM/YYYY hh:mm A'. While running the page, when I pop up the calendar control of the DateTimePicker and try to select any date beyond the minDate and maxDate range using the mouse, the control correctly disables the selection and stops me from selecting any invalid date. However, if I write any invalid date beyond the range by using keyboard, the control isn't validating it, therefore allowing invalid date to pass to the server-side. How do I stop it from doing so?
I'm using the updated versions of moment.js and FontAwesome. I've also tried using min and full versions of Tempus Dominus, moment and FontAwesome separately, yet it's showing date beyond the range of minDate and maxDate. Am I missing something or is it an inherent issue?
My code follows below.
Master page aspx:
Payment page aspx: