After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701215 - Clicking on the X on popped up notifications should not add them to the message tray
Clicking on the X on popped up notifications should not add them to the messa...
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: message-tray
3.8.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-29 18:28 UTC by Stephen Gallagher
Modified: 2015-03-07 05:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephen Gallagher 2013-05-29 18:28:44 UTC
When an incoming notification is displayed at the bottom of the screen, it has an (X) in the upper right corner. When this (X) is clicked, the expected behavior would be that the notification is completely dismissed. Instead, it's enqueued into the message tray, necessitating a second action to actually be rid of it.

Clicking anywhere else on the message switches the context (and possibly workspace) to the application that generated the message. This avoids enqueuing it, but is jarring and interrupts workflow.
Comment 1 Stephen Gallagher 2013-05-29 18:37:00 UTC
Additionally, there is a similar confusing behavior when viewing the message in the message-tray itself. When clicking on the icon, the message is displayed with an (X). I would expect that clicking the (X) would dismiss the message from the queue, but instead I have to right-click on the icon and select "remove" to get rid of it.
Comment 2 Florian Müllner 2013-05-29 18:44:10 UTC
This has nothing to do with classic mode, renaming accordingly.Also see bug 682237 for the original discussion on the behavior.
Comment 3 drago01 2013-05-30 00:29:12 UTC
Also see bug 687016
Comment 4 Florian Müllner 2015-03-07 05:38:32 UTC
The close button has been closing notifications for a while now, and still does with the updated notifications in 3.16.