Re: Event constructor defaults

On Mon, Feb 11, 2013 at 2:58 PM, Glenn Maynard <> wrote:
> Unfortunately, this is already implemented in Firefox and Chrome, but
> changing these defaults might still be still web-compatible.

It's not compatible with the initEvent() API however. Not sure why
there would not be a reason to have a uncancellable event. Making
cancelable indicate whether preventDefault() can actually be used
seems like a net positive. And often canceling events has no effect
(certainly with platform events). The non-bubbling will be a non-issue
once we have better event listeners.


Received on Monday, 11 February 2013 15:12:51 UTC