Closed Bug 117780 Opened 23 years ago Closed 21 years ago

attrChange attribute for Mutation events should not be a random value

Categories

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

x86
Windows 98
defect

Tracking

()

RESOLVED FIXED
Future

People

(Reporter: vladimire, Assigned: hyatt)

Details

If a dom mutation event does not support attrChange attribute there should be
some fixed default value assigned to it. "null" or 0 or "undefined" would be
what I would expect it to have, but instead the value is a random integer.
Mutation stuff for ya, Dave.
Assignee: joki → hyatt
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Priority: -- → P4
I'm pretty sure that bryner fixed in bug 220228. If anyone can reproduce this on
a recent build please reopen this bug.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.