In our application, it's invalid to enter a date that's less than 13 years from today. We don't want to disable elements of its GUI to prevent this. We DO want to NOT update the text input field or invoke onChange while the user navigates to an older year/month.
Undesireable Functionality:
Day view - whenever the user clicks the '<' or '>' to browse to another month, the date gets saved and onChange is invoked.
Month view - whenever the user clicks the '<' or '>' to browse to another year, the date gets saved and onChange is invoked.
Year view - whenever the user clicks the '<' or '>' to browse to another decade, the date gets saved and onChange is invoked.
Changes in this PR:
Day view - whenever the user clicks the '<' or '>' to browse to another month, DON'T save the date or invoke onChange IF closeOnSelect=true, otherwise pre-PR functionality.
Month view - whenever the user clicks the '<' or '>' to browse to another year, DON'T save the date or invoke onChange IF closeOnSelect=true, otherwise pre-PR functionality.
Year view - whenever the user clicks the '<' or '>' to browse to another decade, DON'T save the date or invoke onChange IF closeOnSelect=true, otherwise pre-PR functionality.
In our application, it's invalid to enter a date that's less than 13 years from today. We don't want to disable elements of its GUI to prevent this. We DO want to NOT update the text input field or invoke onChange while the user navigates to an older year/month.
Undesireable Functionality:
Changes in this PR: