DatePicker: Problem with 29/02/2024 (leap year)

[kika73]

DatePicker: Problem with 29/02/2024 (leap year)

[melloware]

You can read more here: https://github.com/primefaces/primefaces?tab=readme-ov-file#community--elite--pro

[kika73]

debugging Primefaces-code shows the problem:

[melloware]

@kika73 i can't reproduce:
pf-11536.zip

Unzip and run mvn clean jetty:run and navigate to http://localhost:8080/primefaces-test/

Edit my reproducer to see if you can make it happen?

[github-actions]

We're unable to replicate your issue, if you are able to create a PrimeFaces Test Reproducer or add details please edit this issue. This issue will be closed if no activities in 20 days.

[kika73]

sorry, my mistake - we used a string and not a date-object

[kika73]

but - i found in documentation, that String is allowed - but then you have the described problem

[melloware]

Can you update my reproducer showing the issue with String?

[kika73]

its not possible to reproduce it with PF 13. UICalendar.validateMinMax(FacesContext context) was changed and the problem is not a problem anymore.
PF 13:

PF 10:

pf-11536-with-string.zip

[melloware]

OK if its fixed in 13 then I will close this issue as we don't backport to 10.x. This is the community tracker only.

[kika73]

so even though we pay for Elite, it won't be fixed for 10.x.x?
Where can I post it to get support for 10.x.x?

[melloware]

This is the community tracker. IF you have PrimeFaces PRO support you can request it through your PRO support. I believe Elite is going away now that we are doing Community released 13.0.5, 13.0.6 etc...