W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2013

Re: [whatwg] Notifications: reviving Notification objects

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 8 Apr 2013 08:04:46 -0700
Message-ID: <CA+c2ei8BHFA1w1s4CSv7+03pFreo54OBqtoJ4=cMJbKNJAye4w@mail.gmail.com>
To: Mounir Lamouri <mounir@lamouri.fr>
Cc: WHAT Working Group <whatwg@lists.whatwg.org>
On Apr 4, 2013 12:53 PM, "Mounir Lamouri" <mounir@lamouri.fr> wrote:
> On 31/03/13 15:33, Anne van Kesteren wrote:
> > There are a couple of scenarios http://notifications.spec.whatwg.org/
> > does not address at the moment.
> >
> > A) User navigates to chat site. Chat site creates a notification from
> > a chat with P while the user does something else. User closes chat
> > site and then navigates to chat site at a later point.
> I guess a better example would be that the website is unloaded on memory
> pressure but the tab is kept. Otherwise, an explicit user action could
> be considered as enough to remove all currently opened notifications.

I don't think that we want to impose the requirement that UAs have to close
all notifications when the user closes the webpage that opened them. Or
that UAs have to do that in order to not have "dangling" notifications.

It seems like a reasonable UI to leave notifications opened once the user
has granted explicit permission for a website to create notifications, as
is the case any time they use the notifications API.

/ Jonas
Received on Monday, 8 April 2013 15:05:19 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:57 UTC