Re: Auto closing of notifications

I'm not particularly comfortable with the response, given the increasing
number of mobile OSes that want to stop running user code and close web
pages without losing state. I'm disappointed that it's out of scope for the
spec, but it's not like I can change that.

On Fri, Nov 21, 2014 at 3:01 PM, Jon Lee <jonlee@apple.com> wrote:

> > On Dec 2, 2013, at 6:15 PM, Jon Lee <jonlee@apple.com> wrote:
> >
> > [This is a draft WG reply to the Jasper's last call comments. Comments
> on the proposed resolution are welcome; if no one objects in a week’s time,
> this will be the WG’s official response to his comment. -Jon]
> >
> > On Oct 23, 2013, at 9:23 AM, Jasper St. Pierre <jstpierre@mecheye.net>
> wrote:
> >
> >> 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?
> >
> > Some notification platforms may track the originating page already; for
> others this might be an unacceptable requirement. What happens after the
> user leaves the originating page is out of scope of the spec.
> >
> > Please let us know promptly whether this response satisfies your
> comments and suggestions.
>
> Given the length of time that has passed since this last comment, I will
> proceed with the assumption that the reviewer has accepted my comments. (If
> you don’t accept them, please let us know!)
>
> Jon
>
>


-- 
  Jasper