ISSUE-57 - Public View
DOM3EV: Attr mutation events optional?
- State:
- CLOSED
- Product:
- DOM 3 Events
- Raised by:
- Bjoern Hoehrmann
- Opened on:
- 2006-03-27
- Description:
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.
- Related emails:
- ISSUE-57: DOM3EV: Attr mutation events optional? (from dean+cgi@w3.org on 2006-03-27)
- Re: ISSUE-57: DOM3EV: Attr mutation events optional? (from jonas@sicking.cc on 2006-03-28)
- Re: ISSUE-57: DOM3EV: Attr mutation events optional? (from robin.berjon@expway.fr on 2006-03-28)
- Re: ISSUE-57: DOM3EV: Attr mutation events optional? (from jonas@sicking.cc on 2006-03-29)
- Minutes 2006-03-27 (from chaals@opera.com on 2006-04-09)
Note: Some of these links may be accessible only to W3C Members.
Related notes:
2006-05-01: The editor takes the 2006-03-27 resolution and subsequent discussion to mean that no change to the document is necessary.