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: ConfirmDialog doesn't render buttons (v18.0.0-rc.1) #16780

Closed
honboubao opened this issue Nov 19, 2024 · 1 comment
Closed

Component: ConfirmDialog doesn't render buttons (v18.0.0-rc.1) #16780

honboubao opened this issue Nov 19, 2024 · 1 comment
Assignees
Labels
Status: Pending Review Issue or pull request is being reviewed by Core Team
Milestone

Comments

@honboubao
Copy link
Contributor

Describe the bug

The confirm dialog doesn't show the Yes and No buttons.

grafik

This can be observed on the beta.3 example page as well https://v18.primeng.org/confirmdialog

The debug console points to an recursion error:

grafik

Environment

Windows 10
Firefox 128.3.1esr

Reproducer

No response

Angular version

18.2.9

PrimeNG version

18.0.0-rc.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

22.4.1

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@honboubao honboubao added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 19, 2024
@mertsincan mertsincan added Status: Pending Review Issue or pull request is being reviewed by Core Team and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Nov 19, 2024
@mertsincan mertsincan added this to the 18.0.0-rc.2 milestone Nov 19, 2024
@mertsincan mertsincan removed this from PrimeNG Nov 20, 2024
@cetincakiroglu cetincakiroglu self-assigned this Nov 21, 2024
@mertsincan mertsincan moved this to Review in PrimeNG Nov 21, 2024
@mertsincan mertsincan removed the status in PrimeNG Nov 21, 2024
@cetincakiroglu cetincakiroglu closed this as completed by moving to Done in PrimeNG Nov 22, 2024
cetincakiroglu added a commit that referenced this issue Nov 22, 2024
@honboubao
Copy link
Contributor Author

I don't think commit 089a01d really addresses the issue. With that change, it will basically always render the default buttons, even if a custom footer is provided, in the latter case it would render both.

I think the issue arises with <ng-template #footer> defining footer as a reference which clashes with @ContentChild(Footer) footer: Nullable<TemplateRef<any>> so I would suggest renaming the variable name of the latter.

The @else if that's been modified in the commit can then be reverted or replaced with a simple @else.

The error with the recursion seems to be a separate issue that arises, when there's nothing in the footer, that's focusable. When I provide a custom footer template containing only text, it shows the same error. If a add a button to the template, it doesn't show the error. This problem should probably be addressed in primeng-dialog focus()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Review Issue or pull request is being reviewed by Core Team
Projects
Status: Done
Development

No branches or pull requests

3 participants