-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
If Signal is open in the background and the tray icon is clicked, focus Signal instead of closing it #6429
Comments
Same here with Signal 6.18.1 on Ubuntu Linux 20.04.6 LTS |
This is also problematic on Linux using a tiling WM such as Hyprland. If the window is already open, clicking the tray icon should simply give that window focus. |
At least on Manjaro Gnome/ Wayland this doesn't seem to be an issue. |
Same issue here on KDE Plasma. This is because the A fix would be quite simple, since there are only two placed where Signal-Desktop/app/SystemTrayService.ts Line 160 in 76a77a9
Signal-Desktop/app/SystemTrayService.ts Line 226 in 76a77a9
I'd open a pull request for this change, if it's acceptable without signing the CLA. |
Thanks for the suggestion @Sajito, I created a PR to tackle this issue. |
Bug Description
If the Signal window is open but not in the foreground (for example, minimized or behind other apps), and I click the systray icon (for example when I receive a new message and it gets a red badge, indicating "clickability"), I expect that Signal comes to the foreground. Instead, it currently closes the app, requiring me to click yet another time to open it.
For all such systray apps, I only ever click the tray icon to open apps, never to minimize them to the tray (I do that using Alt+F4 or similar). I have never had this problem with any other such app.
Steps to Reproduce
Actual Result:
The app is minimized to the systray.
Expected Result:
The app is activated / brought to the foreground.
Platform Info
Signal Version:
6.18.1
Operating System:
Win11 10.0.22621 Build 22621
Linked Device Version:
Not relevant
Link to Debug Log
Hopefully this is trivially reproducible and does not require a log. Let me know if this is not the case.
The text was updated successfully, but these errors were encountered: