search

emersion / mako

A lightweight Wayland notification daemon
https://wayland.emersion.fr/mako
MIT License
2.18k stars 139 forks source link

input to notification goes to originating window #474

Open yogo1212 opened 11 months ago

yogo1212 commented 11 months ago

I've been troubled by two problems:

  1. Clicking notifications didn't do anything
  2. Tabs were disappearing from my browser window, seemingly at random

Today I noticed that that is because my mouse input goes to the window that spawned the notification. Clicking anywhere will just 'fall through' to the part of the window that is occluded by the notification frame (even on on an otherwise empty workspace). For browser notifications, that means I can click on the burger menu, the 'extensions' button, open the 'downloads' pane, or fumble with my Firefox tabs.

  1. Go to https://www.bennish.net/web-notifications.html
  2. Open a notification
  3. Try to click the cogwheel
  4. The burger menu of firefox opens
  5. Switch to a new workspace
  6. Click the cogwheel
  7. The same happens (the burger menu opens despite Firefox being on a different workspace)

I'm on EndeavourOS, there's an exec mako in my config.d/autostart/applications - no other customisation.

emersion commented 11 months ago

Which compositor is this?

mako sets an input region. Maybe the input region does not get handled properly by the compositor.

yogo1212 commented 11 months ago

Hi :-)

Wayland/Sway - forgot to mention :see_no_evil: I've noticed that, after booting, everything works. The problem only occurs after a while and I can reliably reproduce the transition from working -> not working using an external monitor.

Before attaching the monitor, the notification 'works' (the gear is highlighted when hovering the cursor over it). When I attach the monitor (not moving any cursors or windows to it), the strange behaviour starts occurring with the next notification. Notifications that were active before the monitor was plugged in aren't affected by the plugging-in.