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: Default date formatting in the header #13811

Closed
simeonoff opened this issue Jan 10, 2024 · 1 comment · Fixed by #13650
Closed

Calendar: Default date formatting in the header #13811

simeonoff opened this issue Jan 10, 2024 · 1 comment · Fixed by #13650
Assignees
Labels
📆 calendar ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.

Comments

@simeonoff
Copy link
Collaborator

simeonoff commented Jan 10, 2024

Description

The default date formatting in the header differs from the ones in Ignite UI for Angular.

We should agree on default formats for day and month.

Ignite UI for Angular:

  • Day - narrow
  • Month - long

Ignite UI for Web Components:

  • Day - short
  • Month - short

Also, the title always stays at Select Date, while it shows the year in Ignite UI for Angular.

Attachments

image

@simeonoff simeonoff transferred this issue from IgniteUI/igniteui-webcomponents Jan 16, 2024
@simeonoff simeonoff self-assigned this Jan 16, 2024
@simeonoff simeonoff added ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. and removed 🆕 status: new labels Mar 8, 2024
@phuong5
Copy link

phuong5 commented Oct 22, 2024

how to fix the title: "Select Date" ? please!
I fixed it like below but it doesn't work
<ng-template igxCalendarHeaderTitle let-formatCalendar>{{ formatCalendar.year }}</ng-template>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📆 calendar ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants