Closed
Bug 63286
Opened 25 years ago
Closed 25 years ago
Listening to DOMAttrChange on all menus causes crash
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
FIXED
Future
People
(Reporter: aaronlev, Assigned: hyatt)
Details
(Keywords: crash)
If you try to add a simple attribute change mutation event listener to all menus
Mozilla crashes with the message /home/moz/mozilla/dist/bin/run-mozilla.sh: line
72: 7531 Segmentation fault $prog ${1+"$@"}
Debugging with gdb changes the crash message to "Exited normally" so you can't
trace where there error came from.
The crash occurs sometime after the event handler is called the first time, but
before any user input is allowed.
Here's a simple test that reproduces the results:
In navigator.js add these lines to the end of Startup()
var menunodes=document.getElementsByTagName("menu");
for (var count=0; count<menunodes.length; count++)
menunodes[count].addEventListener("DOMAttrModified", handleattributechange,
true);
Then create this function in the same file:
function handleattributechange(evt)
{
dump("**>> menu changed!!!\n");
}
Also note that the special mutation event properties are not set for the evt
parameter given to the handler.
Updated•25 years ago
|
Comment 2•25 years ago
|
||
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
Comment 4•25 years ago
|
||
should no longer be a blocker, ->future
Target Milestone: mozilla0.9 → Future
| Assignee | ||
Comment 5•25 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•