-
Notifications
You must be signed in to change notification settings - Fork 135
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
Application menu occasionally "freaks out" while trying to search for a program #1958
Comments
Do you use Openbox? If yes, can you reproduce it with another WM? |
We are using Openbox, yes. Is there a particular WM I should try? If not, I'll swap to xfwm and see what happens. |
Yes, xfwm is good. |
I am able to reproduce this using xfwm4. I started with Openbox and then launched xfwm4 with |
The way to reproduce is:
I'll make a PR for avoiding navigation while search widgets have focus. |
@ArrayBolt3 Can you, please, check with #2134 ? |
Will do, I'll try to get that done hopefully some time tonight. |
Expected Behavior
If you open the application menu and begin typing, it should search for menu items that match your search term, updating the displayed list of items as you type.
Current Behavior
Every so often, I accidentally manage to get my application menu to do this while searching for an app:
After typing the first three letters or so, one of the menus will suddenly open despite me having not hovered over it, then the "primary" app menu (which only has "Featherpad" in it in the above screenshot) will update to contain only items matching my search term and leave the popped-out menu "floating". When this happens, the keyboard focus inexplicably gets removed from the search text box, making any further keypresses ignored. Furthermore, clicking on the desired app while the menu is in this weird state results in the menu simply closing and no app being launched.
This happens quite often to me (multiple times a day), but it is not reliably reproducible. It happens "when it feels like it", for lack of a better description.
Possible Solution
I don't ever remember this happening on LXQt 0.17.0. I do seem to have noticed it happening since LXQt 1.2.0 at least, maybe even a bit earlier. It might be possible to bisect between those points and find whatever caused this issue.
Steps to Reproduce (for bugs)
System Information
The text was updated successfully, but these errors were encountered: