-
Notifications
You must be signed in to change notification settings - Fork 877
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
focus bug when accessing main menu from floating pane #7952
Comments
Can reproduce. Added the NB25 milestone. Don't think it's urgent enough for NB24. At a guess, if this is caused by #4603 , it might be due to either listening on the wrong property (should be permanent focus owner?) and/or not checking that the focused component is inside a TopComponent. |
…le menu is open Fix apache#7952.
These didn't seem to offer a way out. |
There's #8285 which is pretty small (lots of logging stuff for removal before a final PR); assuming nothing better comes along... Look at Basic problem is that I don't particularly like this solution. But can't think of anything better, possibly a custom focus manager (ouch). Skip Activation (behavior before #4603)DockedCtrl-0
Ctrl-1
Alt-F
FloatingCtrl-0
Ctrl-1
Alt-F
With Activation (behavior after #4603)FloatingCtrl-0
Ctrl-1
Alt-F
|
…le menu is open Fix apache#7952.
Fix apache#7952. Use invokeLater() so KeyboardFocusManager changes are finished. Use "permanentFocusOwner" property (instead of "focusOwner") for minor optimization.
Sleeping on it revealed a better (I think) solution. See #8288. |
This issue should be linked to the proper PR. |
Fix apache#7952. Use invokeLater() so KeyboardFocusManager changes are finished. Use "permanentFocusOwner" property (instead of "focusOwner") for minor optimization.
Fix apache#7952. Use invokeLater() so KeyboardFocusManager changes are finished. Use "permanentFocusOwner" property (instead of "focusOwner") for minor optimization.
Apache NetBeans version
Apache NetBeans 23
What happened
Summary: When making a pane in the NetBeans UI a floating pane (basically a separate window), then invoking the main menu via keyboard from the floating pane changes the focus back to the main window, and the menu loses keyboard focus. In consequence, it's impossible to perform menu actions for items in a floating pane.
This is a regression in NetBeans 16-23. This had worked since at least NetBeans 8 up to NetBeans 15, and stopped working with NetBeans 16.
This bug makes it impractical to use floating panes in conjunction with keyboard navigation and/or to select actions from the main menu that work on items in the floating pane, such as "Close " in the "How to reproduce" example below, or also actions like Team > Commit.
Language / Project Type / NetBeans Component
NetBeans UI, any project type
How to reproduce
What works:
What does NOT work:
Did this work correctly in an earlier version?
Apache NetBeans 15
Operating System
Windows 10
JDK
Any JDK, specifically tested under 8, 11, 17, and 21
Apache NetBeans packaging
Apache NetBeans provided installer
Anything else
This bug may be a side effect of #4603. I had originally already reported this as #5062.
I'm willing to help any way I can in implementing a fix. This is an important issue to me and has held me back from upgrading from NetBeans 15.
Are you willing to submit a pull request?
Not at the moment, but possibly eventually.
The text was updated successfully, but these errors were encountered: