W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2010

Re: stopPropagation() or stopImmediatePropagation() called early

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 18 Feb 2010 18:11:29 -0800
Message-ID: <63df84f1002181811k226f3d89o9584fe8dd56df94c@mail.gmail.com>
To: Doug Schepers <schepers@w3.org>
Cc: "Hallvord R. M. Steen" <hallvord@opera.com>, www-dom@w3.org
The most reasonable thing to do seems that dispatching an event which
has had stopPropagation() or stopImmediatePropagation() called on it
causes no dispatch to happen. I.e. the call to dispatchEvent is a
no-op (other than that if such an event is dispatched again, it raises
an DISPATCH_REQUEST_ERR exception).

/ Jonas

On Thu, Feb 18, 2010 at 3:08 PM, Doug Schepers <schepers@w3.org> wrote:
> Hi, Hallvord-
>
> Hallvord R. M. Steen wrote (on 2/18/10 5:52 PM):
>>
>> Hi,
>> what should happen if event.stopPropagation() or
>> stopImmediatePropagation() are called on an event before dispatch? The
>> spec doesn't seem to cover this.
>
> Thanks for noticing that. I'm happy to specify whatever behavior people
> favor. Any clue what existing implementations do?
>
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG and WebApps WGs
>
>
Received on Friday, 19 February 2010 02:12:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT