GNOME Bugzilla – Bug 707073
Message tray menu is missing the notifications switch
Last modified: 2014-04-14 17:07:20 UTC
This is a regression from previous releases - we used to have a switch which would disable non-urgent notifications. This was included in the mockups for the message tray menu.
When notifications are disabled: * Chat status should be set to Busy * Notification banners should no longer be displayed * Urgent banners should still be displayed * Notifications for adding/removing favourites should still be displayed * If you set your chat status to something other than Busy/Invisible/Offline, notifications should be enabled again
(In reply to comment #1) > When notifications are disabled: > * If you set your chat status to something other than Busy/Invisible/Offline, > notifications should be enabled again Does this still make sense without the integrated status switcher?
(In reply to comment #2) > Does this still make sense without the integrated status switcher? I think it does - the message tray menu provides feedback about your chat status, and you can change it in Empathy. Thinking about it though, the lack of persistent feedback is a concern. In the old design, the chat status indicator in the top bar provided a reminder that notifications are disabled (by showing that your status is busy). We don't have that now, so it's possible that you could disable notifications and forget about it.
not going to happen for 3.10
Created attachment 256095 [details] [review] messageTray: Add 'Notifications' switch to tray menu According to the designs, the notifications switch was supposed to move from the user menu to the new message tray menu. However so far the new system status implementation only removed the old switch, so add it back in its new place now.
*** Bug 709045 has been marked as a duplicate of this bug. ***
Can we get this into a 3.10 point release? It's pretty bad that the old feature was removed before the new one was added to replace it...
It will require a freeze break request (though the string in question has been around from 3.4 to 3.9.x or so) but sure, if we can get this reviewed ...
Review of attachment 256095 [details] [review]: Looks good to me and works fine in testing. And yeah I agree that we should (try) to get this into 3.10.1
please request a freeze break
What happened to this?
Still discussing with the design team ...
Comment on attachment 256095 [details] [review] messageTray: Add 'Notifications' switch to tray menu Attachment 256095 [details] pushed as 6e9a2fe - messageTray: Add 'Notifications' switch to tray menu The designers were concerned about the busy state being too hidden now (e.g. users can forget that they toggled the switch and miss notifications) - we should address this for 3.12, so leaving the bug open.
Hi What about the chat switch that appeared in the design docs? Is that on hold because of the concerns raised by the design team? thanks,
It hasn't landed since the design is to launch the Chat app, and the Chat app isn't completed yet.
*** Bug 709146 has been marked as a duplicate of this bug. ***
FWIW, I think it's very confusing that disabling notifications changes my chat status to Busy. And the same for vice-versa: I actually missed some important notifications because I didn't realize that setting my Empathy status to Busy would cancel them. I don't have anything against the behavior of tying notifications to the Busy status, I just wish the behavior would be more obvious. (I don't have any suggestions as to how to do that.)
(In reply to comment #17) > FWIW, I think it's very confusing that disabling notifications changes my chat > status to Busy. And the same for vice-versa: I actually missed some important > notifications because I didn't realize that setting my Empathy status to Busy > would cancel them. > > I don't have anything against the behavior of tying notifications to the Busy > status, I just wish the behavior would be more obvious. (I don't have any > suggestions as to how to do that.) Don't we show a notification when you disable notifications (oh the irony) to explain this?
(In reply to comment #13) ... > The designers were concerned about the busy state being too hidden now (e.g. > users can forget that they toggled the switch and miss notifications) - we > should address this for 3.12, so leaving the bug open. I've filed bug 707073 for this - seems clearer.
(In reply to comment #19) > (In reply to comment #13) > ... > > The designers were concerned about the busy state being too hidden now (e.g. > > users can forget that they toggled the switch and miss notifications) - we > > should address this for 3.12, so leaving the bug open. > > I've filed bug 707073 for this - seems clearer. Wrong bug number? The number you wrote here is the current bug.
Bug 728160
Oops, sorry!