Welcome to the Angular feedback portal. We’re happy you’re here! If you have feedback on how to improve the Angular, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

0
Votes

When I input invalid date ranges (e.g., 17/01/2025 in the first and 02/01/2025 in the second), the third DatePicker becomes completely disabled.

Even after correcting the dates in the first and second DatePickers to valid values, the third DatePicker remains disabled.


Steps to reproduce:

  • Run the sample.
  • Select any date in the first DatePicker.
  • Select a date in the second DatePicker that is lesser than the date in the first DatePicker.
  • Open the third DatePicker popup (at this point, the overlay class is added correctly and datepicker component becomes disabled).
  • Change the date range to valid values (e.g., select any date in the first DatePicker).
  • Select a date in the second DatePicker that is greater than the date in the first DatePicker.
  • Observe that the third DatePicker remains in a disabled state.

 

Expected Behavior: "e-overlay" class should be removed properly on valid daterange so that datepicker component is interactive

Actual Behavior: "e-overlay" class is maintained even we set the valid daterange using min and max properties