-
-
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
Clicking macOS Notification Doesn't Focus Message Input #5859
Comments
@karlhorky thanks for opening this. As it stands, this is doesn't seem to be a bug report... Could you please open a feature request as described here? Sorry to redirect you! |
Hm, why do you think that it's a feature request? Seems like a pretty big UX bug to me... all other instant messenger apps work this way. Signal is breaking a UX expectation - this, in my eyes, is a bug. What is the justification for labeling this a feature? In addition to that, putting this in the Community Forum like @josh-signal has suggested in #5541 feels like it's just going to disappear into a vast sea of unreviewed posts that the Signal team will never get around to looking at. |
We explicitly focus the message that generated the notification - that's the current design, and likely won't change soon. What you're maybe looking for is CMD+Shift+T, which will take you to the text box so you can type your reply. |
Learning a hotkey is not something that users should have to do - all other messenger apps allow for typing as soon as you click the notification. |
#4998 would be an acceptable alternative, but really focusing the message input is the right UX design decision. |
I guess just another reason to advocate more people to move to Telegram instead of Signal. Too bad that user experience is not a priority! |
Bug Description
When Signal desktop on macOS is not already focused, clicking on a notification doesn't cause the message input to be focused, leading to bad UX for keyboard users
Steps to Reproduce
I tested this also on Windows, and it also occurs there.
Actual Result:
The message input is not focused
Expected Result:
The message input should be focused, and ready to accept input
Screenshots
Platform Info
Signal Version:
5.37.0 Production (M1)
Operating System:
macOS Monterey 12.3.1
Linked Device Version:
5.34.5
Link to Debug Log
Related
Potentially resolved by #4998 (even though the input field should probably just be properly focused instead)
Almost related, but the author did not push for the focus: #4950
The text was updated successfully, but these errors were encountered: