Based on the information in the question, I am not exactly sure what might be causing this unexpected behavior of the DatePicker component.
One possible reason for this behavior might be related to the fact that the developer is setting the min and max properties of the DatePicker component but is not setting its value property. When the value(ngModel) property is left empty, by default the current date is highlighted when the popup is opened. In case the min and max dates don't match the current date, such a view is expected to appear.
In case the provided information does not help you resolve the issue, I would ask you to provide more detailed information about the specifics of the implementation or a runnable demo showcasing the issue so that I can work on a more case-specific solution.
Hi Kumeri,
Thank you very much for the screenshot provided.
Based on the information in the question, I am not exactly sure what might be causing this unexpected behavior of the DatePicker component.
One possible reason for this behavior might be related to the fact that the developer is setting the min and max properties of the DatePicker component but is not setting its value property. When the value(ngModel) property is left empty, by default the current date is highlighted when the popup is opened. In case the min and max dates don't match the current date, such a view is expected to appear.
In case the provided information does not help you resolve the issue, I would ask you to provide more detailed information about the specifics of the implementation or a runnable demo showcasing the issue so that I can work on a more case-specific solution.
Let me know how it goes.
Regards,
Georgi
Progress Telerik