We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When we try to view the calendar component for a period longer than 11 months and it starts on November or December, it does not display correctly.
Tests have been done on the StackBlitz environments for versions 16, 17, 18, and 19, but none of them worked.
Production environment
https://stackblitz.com/edit/2urabfum?file=src%2Fapp%2Fdatepicker-inline-demo.html
18.0.1
18
Angular CLI App
TypeScript
18.20.3
No response
A correct visualization
The text was updated successfully, but these errors were encountered:
Due to PrimeNG team's busy roadmap, this issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨
Sorry, something went wrong.
@DrochCH Calendar is deprecated: https://v18.primeng.org/guides/migration#compatible Use DatePicker instead.
As you can see in the StackBlitz , we are using datepicker. So the issue keeps reproducing
No branches or pull requests
Describe the bug
When we try to view the calendar component for a period longer than 11 months and it starts on November or December, it does not display correctly.
Tests have been done on the StackBlitz environments for versions 16, 17, 18, and 19, but none of them worked.
Environment
Production environment
Reproducer
https://stackblitz.com/edit/2urabfum?file=src%2Fapp%2Fdatepicker-inline-demo.html
Angular version
18.0.1
PrimeNG version
18
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.20.3
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
A correct visualization
The text was updated successfully, but these errors were encountered: