W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2014

Re: [whatwg] Notification's click event should be cancelable

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 26 Aug 2014 12:02:13 +0200
Message-ID: <CADnb78iWdgAShq8MVr7PpvW5KGJvZ03hJW9CkxWe0Q4p=mjxcA@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: atwilson@chromium.org, Robert Bîndar <robertbindar@gmail.com>, 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 Tue, Aug 26, 2014 at 11:53 AM, Jonas Sicking <jonas@sicking.cc> wrote:
> On Tue, Aug 26, 2014 at 2:18 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> It's a somewhat complex design compared to what we probably need long
>> term, if long term is service workers.
>
> I'm not convinced that even with SW, the proper design is to tell
> websites to always funnel click notifications through a SW.

That's the standing proposal. Do you think we should fire them both in
service workers and on Notification objects?


> Alternatively we don't use events here at all. Instead we could use a
> .clicked property which returns a promise. This is a typical "one
> shot" notification where Promises are better suited than DOM Events.

Seems somewhat sensible. Same for closed, error, etc? Not sure how
we'd reconcile that with the existing design.


> However I don't actually think that firing events on multiple
> EventTargets is that complex.


-- 
http://annevankesteren.nl/
Received on Tuesday, 26 August 2014 10:02:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:22 UTC