Re: Auto closing of notifications

Something we added recent in GNOME for desktop apps was support for
persistent notifications. Notifications used to auto-close, because any
actions would be unavailable after the app closed.

The way we solved this was to use DBus activation to send apps a message
when they restart.

I wonder if something similar could be done in the web world; instead of
using live callbacks, have the user agent navigate to a specific URL in the
originating tab / a new tab, which the web app could detect and do things
on?



On Wed, Oct 23, 2013 at 11:52 AM, Anne van Kesteren <annevk@annevk.nl>wrote:

> On Wed, Oct 23, 2013 at 4:37 PM, Andrew Wilson <atwilson@google.com>
> wrote:
> > Applications can also register a window.onclose method to close any
> pending
> > notifications (gmail does this) if that's the behavior they want.
> >
> > I don't think this addresses issues where the window itself crashes or is
> > shutdown due to memory constraints, however. It's not clear to me that we
> > *should* auto-close notifications - I suspect that there are arguments in
> > favor of keeping those notifications open (for example, if my calendar
> web
> > page crashes, should I really miss out on any notifications that were
> > displayed?)
>
> I could see an argument for having some convenience features here.
> E.g. being able to define a timeout when creating a notification.
> However, it seems we should wait a bit longer until there's more
> deployment of this feature to find out what the actual common pain
> points are.
>
>
> --
> http://annevankesteren.nl/
>
>


-- 
  Jasper