Primevue DatePicker DisabledDates doesn't work when in monthly view mode

[barrierwill]

Describe the bug

When using the primevue datepicker in monthly view mode, I want certain months to not be able to be selected. Using the disabledDates prop does nothing for disabling invalid months by the calendar popup and the user can still select invalid dates for the month picker.

It is inconsistent because the user is blocked from typing in an invalid date, but not for selecting the date in the calendar popup.

Pull Request Link

No response

Reason for not contributing a PR

• Lack of time
• Unsure how to implement the fix/feature
• Difficulty understanding the codebase
• Other

Other Reason

No response

Reproducer

https://stackblitz.com/edit/3mrnf6a8?file=src%2FApp.vue

Environment

Its just the environment made from copying one of the date picker stack blitz pages.

Vue version

3.2.45

PrimeVue version

4.2.5

Node version

No response

Browser(s)

No response

Steps to reproduce the behavior

1. Open the calendar.
2. Select February
3. February is filled in as 02/01/2025 even though every day in February is not allowed to be selected.

Expected behavior

I expect the month of February to be disabled because of 2 reasons:

1. Every day in February is disabled, so the calendar selection for February should be disabled.
2. Since the value when clicking on February in the calendar is 02/01/2025, I expect just having the first date of the month being in the disabledDates array will disable the whole month.

Also, if the user manually types in '02/01/2025', it gets cleared out as expected. The user can still choose the date in the datepicker by opening the calendar popup.

If you get rid of the 'view=month' prop on the datepicker, you can see that every date in February is disabled so the user can't choose any date in February at all. With the 'view=month' prop, it doesn't work the same way.

[github-actions]

Thanks a lot for this issue! PrimeTek's own vision for PrimeVue is demanding, but community feedback is crucial in prioritization. The more upvotes help ensure this fix can be addressed quickly or the related PR can be merged soon.

[YannisJustine]

I completely agree with this request. I previously brought up this point in this discussion. I hope this can be considered soon.