You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Receive two notifications so that both are displayed in the corner
Hover the bottom notification (for the bottom corner) or the top notification (for the top corner)
Either close the notification via right-click or the X button, or (presumably, didn't test) open the message with the hovered notification from another device.
Expected behaviour
The other notification moves closer to the corner and the "Hide all" button disappears.
Actual behaviour
The other notification moves closer to the corner and "Hide all" starts disappearing but reappears again when the notification reaches the cursor.
Operating system
Arch Linux, i3 version 4.24
Version of Telegram Desktop
5.9.2
Installation source
Other (unofficial) source
Crash ID
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Hey. Just letting you know that for this issue, unlike other notification issues I've reported recently, I'm not planning to work on a patch, at least any time soon. So, if anyone feels like fixing it, you are welcome.
Btw, Happy New Year, everyone! 🎉
May it be the year of Telegram Desktop bug fixes and awesome user experience improvements!
I really believe there's something is wrong with either your WM or Qt's X11 integration. It might be a good idea for you to switch to Wayland to avoid such weird bugs.
Steps to reproduce
Expected behaviour
The other notification moves closer to the corner and the "Hide all" button disappears.
Actual behaviour
The other notification moves closer to the corner and "Hide all" starts disappearing but reappears again when the notification reaches the cursor.
Operating system
Arch Linux, i3 version 4.24
Version of Telegram Desktop
5.9.2
Installation source
Other (unofficial) source
Crash ID
No response
Logs
No response
The text was updated successfully, but these errors were encountered: