OverlayPanel: After interaction two mouse clicks are needed to close dialog
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react
- Domain
- frontend
Research direction
Start by reproducing the behavior in the linked StackBlitz example and then trace the OverlayPanel entry point and its outside-click handling after an internal button interaction. Done means the first click outside the dialog closes it, with the existing interaction behavior preserved.
Written by the indexing model from the issue text.
Description
Describe the bug
When a button inside an OverlayPanel is clicked, two clicks outside of the dialog are necessary to close the dialog. If no interaction inside the dialog has happened, the dialog can be closed with a single mouse click.
Reproducer
https://stackblitz.com/edit/kt8tihbc
System Information
System:
OS: Linux 7.0 Fedora Linux 43 (Workstation Edition)
CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
Memory: 66.42 GB / 125.46 GB
Container: Yes
Shell: 5.3.0 - /bin/bash
Binaries:
Node: 22.22.2 - /usr/bin/node
Yarn: 4.15.0 - /usr/local/bin/yarn
npm: 10.3.0 - /usr/local/bin/npm
bun: 1.1.4 - /usr/local/bin/bun
Browsers:
Chrome: 148.0.7778.178
Firefox: 151.0.1
Firefox Developer Edition: 151.0.1
Steps to reproduce the behavior
- Open OverlayDialog
- Click a button inside the dialog, e.g. pagination button
- Click outside the dialog - the dialog should be closed but is not
- Click again outside the dialog - the dialog will be closed
Expected behavior
The dialog should be closed on the first click outside of the dialog.
- Dominant language
- CSS
- Stars
- 8.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from primefaces/primereact
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primereact#8552 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
primefaces/primereact#8550 ·
-
Row checkbox selection tick is invisible in Landing Page Theme sectionPossibly taken @Prakash1185 claimed this 172 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
primefaces/primereact#8545 ·
-
Dependency conflict between jspdf v4 and jspdf-autotable during npm installPossibly taken @Kamran92 claimed this 187 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primereact#8537 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
primefaces/primereact#8551 ·
All issues in primefaces/primereact
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
eclipse-tradista/tradista#371 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
devswha/herdr-web-ui#4457 ·
-
bug ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
userFRM/egui-charts#4068 ·
Maintainers usually reply within 1 day