Skip to content
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

Clicking onto another screen doesn't close the menu #525

Open
ChildishGiant opened this issue Nov 30, 2021 · 2 comments
Open

Clicking onto another screen doesn't close the menu #525

ChildishGiant opened this issue Nov 30, 2021 · 2 comments

Comments

@ChildishGiant
Copy link

What Happened?

When clicking off off the menu onto anywhere on the same screen, it closes but this doesn't happen if the next click is on another monitor. I assume this is unintended as if someone clicks off that screen they almost certainly want to close the menu.

Steps to Reproduce

  1. Have two screens
  2. Open app menu
  3. Click to other screen

Expected Behavior

The app menu should close like it does if the click is on the primary monitor.

OS Version

6.x (Odin)

Software Version

Latest release (I have run all updates)

Log Output

No response

Hardware Info

No response

@cassidyjames
Copy link
Contributor

cassidyjames commented Nov 30, 2021

My understanding is that under X, WingPanel actually draws a full-screen invisible window to handle clicking to close popovers. I'm not sure what the plan is moving forward, but it's possible we could drop that if the panel losing focus closed it (so focusing another app would close it), but that would also require that clicking the blank desktop focused it (even though there's no actions when primary-clicked, there's the ability to secondary-click for the desktop menu). However, I'm not sure if the latter would be desired behavior, as it could be weird that it looks like nothing is focused on your workspace.

Another alternative could be having WingPanel draw a blank window on every display to accept clicks, but I think that's bandaging the issue with more X-specific code.

@ChildishGiant
Copy link
Author

Maybe this is blocked by Wayland then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants