W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

Re: ISSUE-57: DOM3EV: Attr mutation events optional?

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 28 Mar 2006 02:15:48 -0800
Message-ID: <44290CD4.30106@sicking.cc>
To: Web APIs WG <public-webapi@w3.org>

Web APIs Issue Tracker wrote:

> ISSUE-57: DOM3EV: Attr mutation events optional?
> http://www.w3.org/2005/06/tracker/webapi/issues/57
> Raised by: Bjoern Hoehrmann
> On product: DOM 3 Events
> There were some issues regarding how mutation events interact with
> Attr nodes and Attr node subtrees. It seems given that Attr nodes
> are Nodes they should behave the same as other nodes, and that is
> what the Note tried to convey. I've made some changes to further
> clarify this. There was a suggestion, however, to make it optional
> for implementations to dispatch mutation events to Attr nodes or
> Attr node descendants since use cases for these are rare and some
> implementations might be able to gain performance benefits from
> doing so. We should continue to allow this since in some imple-
> mentations it might be more difficult not to dispatch them and it
> is not unimportant for some use cases, generally DOMAttrModified
> is sufficient however.

Since attribute nodes never has a parent, no mutation events should ever 
bubble up from them.

Of course, there is the issue of bubbling events from the textnode 
inside the attribute to the attribute. I don't think I care too much 
either way on this one since I believe it would be relativly easy to 
implement in mozilla, not sure how other implementors feel though.

/ Jonas
Received on Tuesday, 28 March 2006 10:15:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:20 UTC