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 775878 - Notifications seems automatically removed shortly after creation
Notifications seems automatically removed shortly after creation
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: Web Applications
3.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-09 12:19 UTC by Bastian Ilsø
Modified: 2016-12-09 16:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastian Ilsø 2016-12-09 12:19:52 UTC
I try to keep notifications turned on for my web applications and this works well. The notification banners show up. According to the GNOME 3 HIG[1], notifications should persist after having initially displayed. However, in all my web applications it seems like the notifications remain in the notification tray only for a few seconds and then disappears. 


I want to keep my notifications around until I have time to check them in the notification tray. Removing notifications automatically after some timeout is a very suboptimal behavior for me because I miss out on all of them.


[1]: https://developer.gnome.org/hig/stable/notifications.html.en
Comment 1 Michael Catanzaro 2016-12-09 16:53:31 UTC
So websites get to decide for themselves when to remove notifications by calling Notification.close(). Many websites intentionally remove notifications after a few seconds; I agree it's generally silly to do that, but if you don't like it, got to complain to the website in question. Do you have example JS where a notification gets withdrawn improperly? I was testing this just a couple weeks ago and it seemed to work fine: notifications would stay forever unless explicitly withdrawn.

Anyway, if there were a bug here, it would be a WebKit bug. So if you have example JS that doesn't work properly, please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.
Comment 2 Michael Catanzaro 2016-12-09 16:54:47 UTC
Note that we do have a couple mildly-related notification bugs:

https://bugs.webkit.org/show_bug.cgi?id=163366
https://bugs.webkit.org/show_bug.cgi?id=164771