Andreas Wuest wrote:
Hi
On 25.6.2006 22:06 Uhr, Greg Amerson wrote:
Hello all,
I'm embedding the Mozilla editor in an application and I have noticed
that mozilla doesn't fire DOMNodeInserted or DOMNodeRemoved events for
radio or checkbox input elements. However, the correct mutation
events are fired for all other types of nodes to my knowledge. I
wonder what is going on with checkbox and radio.
Have you tried using nsIEditActionListener?
When I originally began my mozilla editor application several months
ago, I looked at using this interface. At the time I was comparing the
callbacks of a nsIEditActionListener against just the 4 DOM mutation
events supported by mozilla. My thinking was that is would be easier
for my application to listen to the 4 DOM mutation events on the root
#document node, than to handle to the 16 callbacks of the
nsIEditActionListener. Only until recently did I find out that the DOM
mutation events for the #document object would have several gaps for
when particular nodes, like checkbox, radio, or any disabled input element.
Now I know that the nsIEditActionListener is only listener interface
that will give me visibility into everything the editor is doing. So I
will be converting over to this interface in short order. Thanks for
the reminder.
However, I was wondering what is the usefulness of the
nsIEditActionListener have callbacks for "will" and then "did" for the
same user edit? Can you prevent the user to performing a edit by doing
something special in the "will" callback? Or are the callbacks split
out into 2 groups incase the editor can't perform the user edit that it
was trying to? So is it possible that the "did" callback after the user
edit has been processed won't always match "will" callback before the
user edit?
_______________________________________________
dev-tech-editor mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-editor
