Open Bug 679582 Opened 15 years ago Updated 5 years ago

DOMSubtreeModified fires too early

Categories

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

6 Branch
x86_64
Windows 7
defect

Tracking

()

People

(Reporter: philspam, Unassigned)

References

Details

(Keywords: regression)

Attachments

(1 file)

663 bytes, application/octet-stream
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20100101 Firefox/6.0 Build ID: 20110811165603 Steps to reproduce: Removed a DOM element. Actual results: DOMSubtreeModified fired on an ancestor element before the element was removed. Expected results: Per the specification, DOMSubtreeModified should fire after the element is removed, the same way it does in Gecko versions < 6
Attached file Testcase
Attaching testcase. Reports the number of childnodes after a DOMSubtreeModified event. Firefox 4 and 5 both report 0, while Firefox 6 reports 1.
Regression window(cached m-c hourly) Works: http://hg.mozilla.org/mozilla-central/rev/cc57061c1258 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a1) Gecko/20110509 Firefox/6.0a1 ID:20110509120627 Fails: http://hg.mozilla.org/mozilla-central/rev/0abb7330c64c Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a1) Gecko/20110509 Firefox/6.0a1 ID:20110509130856 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=cc57061c1258&tochange=0abb7330c64c Triggered by: Bug 650493 - Simplify mutation events and userdata handlers
Blocks: 650493
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Assignee: nobody → jonas
Is this something that is still being investigated or fixed?
Flags: needinfo?(jonas)
I'd rather not make any changes to mutation events until there is a proper spec agreed upon by all major browsers. Right now there's lots of subtle differences and it's not clear who's right since the spec is very vague.
Assignee: jonas → nobody
Flags: needinfo?(jonas)
Any changes that we make at this point is likely to break more content than it fixes, so we should only do it if we're confident that we won't have to change it again, and that it aligns with other browsers so that everyone is pulling in the same direction.

Bulk-downgrade of unassigned, 4 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: