- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 25 Aug 2014 09:42:08 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: atwilson@chromium.org, whatwg <whatwg@whatwg.org>, Olli Pettay <olli@pettay.fi>, Jake Archibald <jaffathecake@gmail.com>, Michael Henretty <michael.henretty@gmail.com>, Peter Beverloo <beverloo@google.com>
On Mon, Aug 25, 2014 at 1:29 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Sun, Aug 24, 2014 at 11:18 AM, Olli Pettay <olli@pettay.fi> wrote: >> Given the very odd Notification API, where the same user input may end up >> being >> represented by several click events in the browser... >> (I think we need to change that somehow, if possible) >> ...cancelling any of the events should cancel the default action. > > We could also make it so that each notification has exactly one > Notification object. And only service workers get a Notification.get() > API and multiple objects per notification, with the tradeoff that > those objects are not event targets as the events go to the service > worker directly. That might simplify things a bit. I definitely think we need the ability for code running in Windows (i.e. code that handles UI) to be able to enumerate any notifications created by the website. / Jonas
Received on Monday, 25 August 2014 16:43:05 UTC