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
When minDate is set for the datePicker, a mdDatepickerMin error should be raised only if the date is earlier than the minDate.
What is the current behavior?
For the moment, when setting minDate, the date for exactly min date is NOT unselectable, which means you can select it, but it nevertheless raises an error. I think it should be either unselectable and raise an error or selectable and not raise the error.
What are the steps to reproduce?
Set up a minDate restiriction for the datepicker and try to select the exact min date, and check the fact that it raises an error while it is still selectable.
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4, Material 2
Is there anything else we should know?
The text was updated successfully, but these errors were encountered:
Bug, feature request, or proposal:
Bug
What is the expected behavior?
When minDate is set for the datePicker, a mdDatepickerMin error should be raised only if the date is earlier than the minDate.
What is the current behavior?
For the moment, when setting minDate, the date for exactly min date is NOT unselectable, which means you can select it, but it nevertheless raises an error. I think it should be either unselectable and raise an error or selectable and not raise the error.
What are the steps to reproduce?
Set up a minDate restiriction for the datepicker and try to select the exact min date, and check the fact that it raises an error while it is still selectable.
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4, Material 2
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: