W3C home > Mailing lists > Public > public-web-notification@w3.org > December 2013

Re: [draft] Auto closing of notifications

From: Jon Lee <jonlee@apple.com>
Date: Mon, 02 Dec 2013 18:13:26 -0800
Message-id: <DDBCAB06-03FC-42DC-9344-4E87ADEC17D3@apple.com>
To: naruse@airemix.jp, public-web-notification <public-web-notification@w3.org>
[This is a draft WG reply to the Yui's last call comments. Comments on the proposed resolution are welcome; if no one objects in a weeks time, this will be the WGs official response to his comment. -Jon]

On Oct 23, 2013, at 5:00 AM, 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

Some user agents may want to keep notifications persistent after a tab has been closed. Introducing this restriction would prevent user agents from providing such an implementation. Moreover, some notification platforms may not allow UAs to do this in the first place.

> * add expire to notification and browsers should close it after expired

This would require browsers to keep track of notifications that have been sent, and may be an unacceptable requirement on some notification platforms.

Please let us know promptly whether this response satisfies your comments and suggestions.

Received on Tuesday, 3 December 2013 02:14:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:14 UTC