Skip to content
New issue

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

Calendar defaultDate is not highlighted #14633

Closed
clementdessoude opened this issue Jan 25, 2024 · 4 comments
Closed

Calendar defaultDate is not highlighted #14633

clementdessoude opened this issue Jan 25, 2024 · 4 comments
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@clementdessoude
Copy link

clementdessoude commented Jan 25, 2024

Describe the bug

I'm not sure if it is a bug or if I don't understand the documentation properly. I tried to use the defaultDate property on the calendar component. The calendar open on the month and year of the defaultDate, as expected, but I expected to see also the defaultDate option highlighted (as the today's date is highlighted by default).

My understanding of the documentation is the same:

Set the date to highlight on first opening if the field is blank.

Screenshot 2024-01-25 at 16 46 27

Environment

My application is running on Angular 17 with latest version of PrimeNg (17.4.0)

Reproducer

No response

Angular version

17.0.9

PrimeNG version

17.4.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

v20.11.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Add a calendar input in your Angular project with a default date (e.g. new Date('1995-12-17T03:24:00');)
  2. Open the calendar input. You should see the month of December, 1995.
  3. The 17th of December however is not highlighted

Expected behavior

I would expect to see the default date highlighted, as the today's date is. Or to have a clearer documentation on this property

Please let me know if I can help in any way on this topic !

@clementdessoude clementdessoude added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 25, 2024
@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 5, 2024
@arnoudb
Copy link

arnoudb commented Feb 26, 2024

We are experience the same issue (angular 17.0.9, primeNG: 17.3.2)

@nbrown-ScottLogic
Copy link
Contributor

I believe this is covered in the bug issue : #2799

Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Aug 25, 2024
Copy link

github-actions bot commented Sep 1, 2024

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

4 participants