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

Dialog: DialogProps missing footerClassName #5661

Closed
iantrudell opened this issue Dec 29, 2023 · 0 comments · Fixed by #5663
Closed

Dialog: DialogProps missing footerClassName #5661

iantrudell opened this issue Dec 29, 2023 · 0 comments · Fixed by #5663
Assignees
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Milestone

Comments

@iantrudell
Copy link

Describe the bug

Dialog has headerClassName and contentClassName available in DialogProps, but no footerClassName.

Reproducer

No response

PrimeReact version

10.2.1

React version

18.x

Language

TypeScript

Build / Runtime

Vite

Browser(s)

All

Steps to reproduce the behavior

No response

Expected behavior

No response

@iantrudell iantrudell added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 29, 2023
melloware added a commit to melloware/primereact that referenced this issue Dec 30, 2023
@melloware melloware self-assigned this Dec 30, 2023
@melloware melloware added Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Dec 30, 2023
@melloware melloware added this to the 10.2.2 milestone Dec 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants