- From: Andrew Wilson <atwilson@google.com>
- Date: Wed, 23 Oct 2013 17:37:05 +0200
- To: "NARUSE, Yui" <naruse@airemix.jp>
- Cc: public-web-notification <public-web-notification@w3.org>
Received on Wednesday, 23 October 2013 15:37:33 UTC
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?) On Wed, Oct 23, 2013 at 2:00 PM, NARUSE, Yui <naruse@airemix.jp> wrote: > Hi, > > If I want to close notifications automatically, the spec says writing > following code: > > notification.onshow = function() { setTimeout(notification.close, 15000) > } > > But when I use a tabbed web browser, and if I close the tab before the > notification is closed, > the notification remains forever (until I close it manually). > > Therefore some actions are needed like: > * web browsers should close notifications when original tab is closed > * add expire to notification and browsers should close it after expired > > thanks, > > -- > NARUSE, Yui <naruse@airemix.jp> > >
Received on Wednesday, 23 October 2013 15:37:33 UTC