W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2011

Re: ISSUE-145 (event handler ordering): Ordering event handlers registered by different means [DOM3 Events]

From: Jacob Rossi <Jacob.Rossi@microsoft.com>
Date: Wed, 3 Aug 2011 17:22:21 +0000
To: "www-dom@w3.org" <www-dom@w3.org>, Sergey Ilinsky <sergey@ilinsky.com>
Message-ID: <D0BC8E77E79D9846B61A2432D1BA4EAE03407055@TK5EX14MBXC287.redmond.corp.microsoft.com>
Hi Sergey,

Following up on this issue, the spec now has a reference to HTML5 where this behavior is defined. Let us know if you have additional comments/concerns with this change.

Thanks,

Jacob

==============================================
From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Wed, 6 Oct 2010 01:13:05 -0700
Message-ID: <AANLkTi=QZ9X5yLmtkoZdcn2FnNh_H1UgWoeA3Oms6WFA@mail.gmail.com>
To: Web Applications Working Group WG <public-webapps@w3.org>
On 10/5/10, Web Applications Working Group Issue Tracker
<sysbot+tracker@w3.org> wrote:
>
> ISSUE-145 (event handler ordering): Ordering event handlers registered by
> different means [DOM3 Events]
>
> http://www.w3.org/2008/webapps/track/issues/145
>
> Raised by: Doug Schepers
> On product: DOM3 Events
>
> Sergey Ilinsky in
> <http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0192.html>:
> [[
> Has the issue of ordering execution of handlers added by the following means
> been addressed?
> a) node.oneventx = f;
> b) node.setAttribute("eventx", f)
> c) node.addEventListener("eventx", f)
>
[...]

Yes. I explained this in thread "event.returnValue", which was
filtered out. Then Hallvord reposted to the list and cc'd me, and it
was again filtered. Then Hallvord I believe reposted my post with a
bcc to me and it made it.

The thread (please look it up) explains that order is covered in HTML 5.

Garrett
Received on Wednesday, 3 August 2011 17:22:51 GMT

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