- From: Olli Pettay <olli@pettay.fi>
- Date: Sun, 24 Aug 2014 12:18:40 +0300
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: whatwg <whatwg@whatwg.org>, atwilson@chromium.org
On 08/24/2014 09:53 AM, Anne van Kesteren wrote: > On Fri, Aug 15, 2014 at 2:38 PM, Olli Pettay <olli@pettay.fi> wrote: >> in order to prevent whatever default action Notification's click event has >> (for example focus the tab which initiated the Notification), the click >> event >> should be cancelable so that .preventDefault() can be called. >> >> Some background >> https://bugzilla.mozilla.org/show_bug.cgi?id=874050&mark=25-26#c25 >> https://bugzilla.mozilla.org/show_bug.cgi?id=1009190#c0 > > Given that a single notification can be represented by many > Notification objects, what kind of semantics are you expecting? A > single listener setting the canceled flag causing any action to not be > done? > > 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. -Olli
Received on Sunday, 24 August 2014 09:19:22 UTC