Closed Bug 72730 Opened 24 years ago Closed 24 years ago

Mutation Events when using Listener causes Crash

Categories

(Core :: DOM: Events, defect)

defect
Not set
critical

Tracking

()

VERIFIED FIXED
mozilla0.9

People

(Reporter: pbwiz, Assigned: hyatt)

Details

(Keywords: crash, testcase)

Attachments

(1 file)

I have created an HTML page to test the 7 Mutation events. Of the seven only 3 respond (DOMNodeInserted, DOMNodeRemoved, and DOMAttrModified). When these three respond to an event more than once Mozilla crashes. It does not happen (normally) on the first try, but if you repetitivaly cause the event it always crashes. In this page I have seven paragraphs which I attach two event listeners each, the click event and one mutation event listeners. The click event modifies the paragraphs subtree which should fire the mutation event attached. If I have implemented this wrong for the 4 mutation events that do not work I would like the test case modified and posted so that they do work. Below is the test case. Jeff Yates.
Note: this effect was noticed on build 2001031604 AND 2001021508 Jeff.
Adding crash keyword.
Keywords: crash
Confirmed Platform: PC OS: Linux 2.2.17 Mozilla Build: 2001032505 Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
OS: other → All
Hardware: PC → All
Hyatt gets mutation event bugs.
Assignee: joki → hyatt
Yay!
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
Only 4 of the 7 are implemented, so this is expected for 3 of them. One that I thought I had working (but that I apparently don't) was CharacterDataModified. I suggest you file another bug on me for the 3 unimplemented mutation events (SubtreeModified, NodeInsertedIntoDocument, NodeRemovedFromDocument). You could also do me a huge favor by testing all of the values of the event as specified in the spec to ensure that I got those right.
Hyatt, I will put in a bug for the three right now.... About testing all of the values, ummm they don't work. Every time I capture the event the browser crashes. Run the test cases on the 3 you think are working and you will see that they work a few times but then crash the browser. I will try testing some more but until you find out what is causing the crash it is about a waste of time. Will write and post test cases for only one mutation event at a time. I will post the 4 that are implemented here and the three on the other bug reports. Jeff.
Fixed. I also patched CharacterDataModified so that it works again.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Target Milestone: mozilla0.9.1 → mozilla0.9
Verifying fixed on build 2001-04-10-04-trunk
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: