- From: Peter Beverloo <beverloo@google.com>
- Date: Fri, 16 May 2014 15:02:28 +0100
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: WHATWG <whatwg@whatwg.org>
On Fri, May 16, 2014 at 2:57 PM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Thu, May 15, 2014 at 6:12 PM, Peter Beverloo <beverloo@google.com> > wrote: > > For |notificationshow|, there is a worry here that if we decide to > support > > delayed notifications, it would enable developers to use notifications to > > set precise timers: create a delayed notification to be displayed an hour > > from now, get the |notificationshow| event, and call > > |notification.close()|. This is something which I'd hope would only be > > possible through some kind of alarms API, which in itself may be > > undesirable to start with. > > Delayed notifications seems like a new feature of sorts we should > probably discuss separately. Although now you can create Notification > objects from a service worker you could get them as the result of e.g. > a server push so maybe it's not so new as it could be polyfilled in > that way... > Keeping possible future additions in mind allows us to avoid ending up with a precise alarms-like API if and when we decide to do so. Beyond that, the subject of delayed notifications indeed is a separate discussion. Service worker integration makes sense to me. I guess I'll wait with > updating the Notifications API until that is further along. > Do you have a specific milestone in mind? Thanks, Peter > > > -- > http://annevankesteren.nl/ >
Received on Friday, 16 May 2014 14:20:46 UTC