-
Notifications
You must be signed in to change notification settings - Fork 869
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
Modal dialog with wrong parent can lock up the application #5987
Comments
Please check with NetBeans 18 - there have been some changes in this area eg. #5280 Be good to see if the issue is still relevant. |
Thanks for pointing that out @neilcsmith-net, but the change to |
Yes, the changes directly in There's no need to open an issue if you have a PR ready anyway. Let's take the conversation there. |
… parent to allow parents in non-active windows as long as the active window is not modal.
This reverts commit d7474cf. Revert "apache#5987: Use the currently active dialog as the presenter parent." This reverts commit d1ac397.
Apache NetBeans version
Apache NetBeans 17
What happened
DialogDisplayerImpl.notify
sets the wrong parent when the currently active window is a modal dialog. When running with FlatLaf providing window decorations viasetDefaultLookAndFeelDecorated
on Linux, this allows the user to click the previously active modal dialog to bring it to the front due to JDK-8306001.How to reproduce
Start a platform application with the following run before creating any UI (e.g. in an override of
ModuleInstall.validate
):Then from within an open model dialog invoke another using
DialogDisplayer.notify
and click the originally open dialog. This dialog will come to the front and if the new dialog is completely hidden there is nothing the user can do but kill the application.Did this work correctly in an earlier version?
No / Don't know
Operating System
Linux
JDK
JDK 17
Apache NetBeans packaging
Apache NetBeans platform
Anything else
No response
Are you willing to submit a pull request?
Yes
The text was updated successfully, but these errors were encountered: