Mutation events are already supported by Xerces-J. I assume you're
talking about Xerces-C, is that right?
Both Xerces-J and Xerces-C supports some user data mechanism. How is
your "user data extension" different?
--
Arnaud Le Hors - IBM Cupertino, XML Technology Group
Hi John,
Yes it would be interesting to look at your version of user data
extensions and work on Mutation Events.
Maybe you could send a note describing both of those items
and post you patch.
I can not offer you to review your code this week because I am
on vacation but maybe next week or other
the agenda: I desparately need
an implementation of Mutation Events and
would like to code it for Xerces. Is there
anyone interested this or anyone with advice
on where to start or on the what not to do's
of such a project.
Thanks
-John
Hi,
> Events in the DOM can "bubble" up the tree. Section 6.2.3 of the
> candidate recommendation specification describes how this works.
> But the important thing is that you only have to register your
> listener on the root and not on *every* node.
>
> Section 6.6.4 from the specification tells
Gerd Mueller wrote:
> But if I understand the specification and the implementation of Xerces right I
> have to add event listeners for _each_ mutation event type to _every_ node of
> the tree to be notified of any mutation - is this right ?
Events in the DOM can "bubble" up the tree. Section 6.2.3
Hi,
I've got a question regarding the mutation events:
I write an application which needs to be notified about _any_ mutation of a
DOM tree and I think the DOM event model is suitable to handle this (?).
But if I understand the specification and the implementation of Xerces right I
ha
