Open Bug 149620 Opened 23 years ago Updated 2 years ago

DOMSubtreeModified does not bubble up to xbl handler

Categories

(Core :: DOM: Events, defect, P5)

x86
Linux
defect

Tracking

()

People

(Reporter: justink, Unassigned)

References

Details

Attachments

(2 files, 1 obsolete file)

Inserting a node into the xbl element DOMSubtreeModified event does not trigger the event in the xbl's handler. <handler event="DOMSubtreeModified" action="alert('inserted');"/> The action alert will never be called. Changing the event to DOMNodeInserted, however, does trigger the action.
status of this?
good question. will hack up a quick test this evening and post results ...
Attached file testcase for DOMSubtreeModified (obsolete) —
testcase, as simple as I could make it
The test case is rather simple. Just extract the tarball and enter file:///path/to/bug149620.xul in the url bar. Click the Add button and it calls the Add() method in the xbl element, which in turn modifies the xml dom tree by inserting another label into the anonymous content. There are two handlers in the binding. The DOMNodeInserted event is commented out. If you comment out the DOMSubtreeModified handler and uncomment DOMNodeInserted handler, then the alert will popup. However, no alert will popup on the DOMSubtreeModified handler. I can only assume this is because the event is either never dispatched or does not correctly travel up the dom tree.
Oh man, sorry, I forgot, that event is not implemented yet... *** This bug has been marked as a duplicate of 74218 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verifying
Status: RESOLVED → VERIFIED
Attachment #98259 - Attachment is obsolete: true
According to this testcase, XUL doesn't support the DOMSubtreeModified event listener properly.
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.6a) Gecko/20031009
Assignee: joki → events
QA Contact: vladimire → ian
Status: UNCONFIRMED → NEW
Ever confirmed: true
Incidentally, I see some funky breakage of replaceChild() in DOM Inspector.
Depends on: 223349
Assignee: events → nobody
QA Contact: ian → events
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: