-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
Status: Needs TriageIssue will be reviewed by Core Team and a relevant label will be added as soon as possibleIssue will be reviewed by Core Team and a relevant label will be added as soon as possible
Description
Describe the bug
Changing dismissable prop after OverlayPanel is visible, doesn't alter the behaviour.
Reproducer
https://stackblitz.com/edit/vitejs-vite-atntbqzz?file=src%2FApp.tsx
System Information
System:
OS: Windows 11 10.0.22631
CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
Memory: 14.70 GB / 31.67 GB
Binaries:
Node: 24.6.0 - C:\Program Files\nodejs\node.EXE
Yarn: 4.9.2 - C:\Program Files\nodejs\yarn.CMD
npm: 11.5.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 144.0.7559.97
Edge: Chromium (142.0.3595.90)
Firefox: 138.0.1 - C:\Program Files\Mozilla Firefox\firefox.exe
Internet Explorer: 11.0.22621.3527
npmPackages:
primereact: ^10.9.7 => 10.9.7
react: ^19.2.3 => 19.2.3
tailwindcss: ^4.1.18 => 4.1.18Steps to reproduce the behavior
- Click "Open overlay"
- Click "Toggle dismissable" inside the overlay
- See that the dismissable state is changed to false
- Click outside the overlay
- See that the overlay closes
Expected behavior
Would expect OverlayPanel to use the current state of dismissable, to decide if it should close. This would align with they way closeOnEscape reacts.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Status: Needs TriageIssue will be reviewed by Core Team and a relevant label will be added as soon as possibleIssue will be reviewed by Core Team and a relevant label will be added as soon as possible