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: Dialog moves to another position instead of closing after pressing close button #15022

Closed
bytebruno opened this issue Mar 12, 2024 · 0 comments · Fixed by #15345
Closed
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@bytebruno
Copy link

Describe the bug

Dialogs with defined position has a buggy behavior sometimes when you press the close button. The expected behavior would be to close the dialog but the dialog moves further to the initial defined position.

chrome-capture-2024-3-12

Environment

You can find this issue on primeng documentation: https://primeng.org/dialog#position

Windows 10
Chrome Version 122.0.6261.112 (Official Build) (64-bit)

Reproducer

https://primeng.org/dialog#position

Angular version

17.1.1

PrimeNG version

17.10.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

Any

Browser(s)

Chrome Version 122.0.6261.112 (Official Build) (64-bit)

Steps to reproduce the behavior

  1. Go to https://primeng.org/dialog#position
  2. Open any positioned dialog
  3. Try some clicks on close button
  4. The dialog sometimes moves further to the initial position

Expected behavior

Once we click dialog close button, the dialog should always close instead of moving itself to any position.

@bytebruno bytebruno added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 12, 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 Mar 18, 2024
@cetincakiroglu cetincakiroglu added this to the 17.15.0 milestone Apr 26, 2024
cetincakiroglu added a commit that referenced this issue Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants