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 764520 - overlay notifications stack up in weird way
overlay notifications stack up in weird way
Status: RESOLVED OBSOLETE
Product: gnome-boxes
Classification: Applications
Component: general
3.20.x
Other Linux
: Normal minor
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-04-03 06:26 UTC by Christian Hergert
Modified: 2018-01-11 10:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stacked notifications (758.57 KB, image/png)
2016-04-03 06:26 UTC, Christian Hergert
Details

Description Christian Hergert 2016-04-03 06:26:07 UTC
Created attachment 325250 [details]
stacked notifications

Screenshot attached. Not sure I have a suggestion on a better way to show this, just found it a bit weird when pruning old VMs.
Comment 1 Jakub Steiner 2016-04-05 17:28:36 UTC
when deleting multiple boxes, the undo action should apply for the combined selection. The notifcations should not be triggered individually.
Comment 2 Zeeshan Ali 2016-04-05 17:40:59 UTC
(In reply to Jakub Steiner from comment #1)
> when deleting multiple boxes, the undo action should apply for the combined
> selection. The notifcations should not be triggered individually.

Yes, it does not if you delete them in one action. Christian deleted them one by one very quickly, I think. It's a bit of a corner case but it can easily happen.
Comment 3 Jakub Steiner 2016-04-05 17:43:30 UTC
Then I think opening up a new in-app notification should be preceded by immediate dismissal of the previous one.
Comment 4 Zeeshan Ali 2016-04-05 17:58:21 UTC
(In reply to Jakub Steiner from comment #3)
> Then I think opening up a new in-app notification should be preceded by
> immediate dismissal of the previous one.

Hmm.. for all notifications? That might cause some serious bugs if we are not extremely careful. For example we automatically delete live boxes if they are shutdown and no installation takes place on the disk during the live session. I guess the solution in this particular case would be to ensure we only provide one notification but my point is that we need to be very careful when implementing this.
Comment 5 Felipe Borges 2017-02-09 12:21:22 UTC
In order to guide the solution of this issue, take a look at:

https://wiki.gnome.org/Design/OS/InAppNotifications
https://bugzilla.gnome.org/show_bug.cgi?id=763292
Comment 6 Felipe Borges 2017-03-06 15:55:17 UTC
(In reply to Zeeshan Ali (Khattak) from comment #4)
> (In reply to Jakub Steiner from comment #3)
> > Then I think opening up a new in-app notification should be preceded by
> > immediate dismissal of the previous one.
> 
> Hmm.. for all notifications? That might cause some serious bugs if we are
> not extremely careful. For example we automatically delete live boxes if
> they are shutdown and no installation takes place on the disk during the
> live session.

I guess this is more of a corner case than all the other situations which cause the notifications to stack up. What do you all think?
Comment 7 GNOME Infrastructure Team 2018-01-11 10:43:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/95.