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

Component: DatePicker [primeng v18] #16368

Open
Torquin opened this issue Sep 11, 2024 · 1 comment
Open

Component: DatePicker [primeng v18] #16368

Torquin opened this issue Sep 11, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Milestone

Comments

@Torquin
Copy link

Torquin commented Sep 11, 2024

Describe the bug

In the new primeng v18 beta the datePicker with the attribute [showButtonBar]="true" breaks the app.

Environment

primeng v18 showcase

Reproducer

https://v18.primeng.org/datepicker#buttonbar

Angular version

18.2.3

PrimeNG version

18.0.0-beta.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

22.8.0

Browser(s)

No response

Steps to reproduce the behavior

Click on input with buttonbar enabled

Expected behavior

Should show button bar with today and clear buttons displayed in the footer

@Torquin Torquin added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Sep 11, 2024
@cetincakiroglu cetincakiroglu added this to the 18.0.0-rc.1 milestone Oct 26, 2024
@Torquin Torquin closed this as completed Nov 7, 2024
@Torquin
Copy link
Author

Torquin commented Nov 7, 2024

The buttons to navigate by month (prev, next) trigger a console error :
core.mjs:7875 ERROR TypeError: Cannot read properties of null (reading 'focus') at DatePicker.updateFocus (primeng-datepicker.mjs:2520:142)

I think this is due to the fact it tries to target : '.p-datepicker-prev' which is now called '.p-datepicker-prev-button'

@Torquin Torquin reopened this Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants