Replies: 1 comment 3 replies
-
Huh. How does it work on other WMs? I'm guessing they put it into the floating layer based on non-resizability, but you still have the manually close issue? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Niri 0.1.6 behavior of Chrome browser notifications from e.g. Slack notifications is very disruptive and hard to work with. Right now, every notification creates a new column to the right, with a new window showing the message there. That window steals the focus (interrupting my typing), and needs to be closed with the tiny [x] in the corner (no ESC etc).
You can test this at https://www.bennish.net/web-notifications.html
Anyone have a good idea of how to improve on this?
It seems Chrome developers have completely abandoned using native desktop notifications. (https://issues.chromium.org/issues/41496153 and https://www.reddit.com/r/chrome/comments/t551ib/comment/hz84t81/?utm_source=reddit&utm_medium=web2x&context=3 and https://www.reddit.com/r/chrome/comments/t5o39l/how_to_turn_chrome_native_notifications_back_on/ and https://issues.chromium.org/issues/41292312)
Window rules, maybe?
niri msg -j focused-window
tells me the popup doesn't really identify itself well:{"title":"","app_id":""}
, so this seems impossible.Firefox uses desktop notifications for popups, and is much more pleasant with niri.
See also:
Beta Was this translation helpful? Give feedback.
All reactions