- From: Jon Lee <jonlee@apple.com>
- Date: Fri, 21 Nov 2014 15:02:30 -0800
- To: naruse@airemix.jp, public-web-notification <public-web-notification@w3.org>
- Message-id: <BB74567B-7565-473A-BB49-0D43B6A15FA2@apple.com>
> On Dec 2, 2013, at 6:13 PM, Jon Lee <jonlee@apple.com> wrote: > > [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 week’s time, this will be the WG’s official response to his comment. -Jon] > > On Oct 23, 2013, at 5:00 AM, NARUSE, Yui <naruse@airemix.jp <mailto: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. 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
Received on Friday, 21 November 2014 23:02:58 UTC