Closed
Bug 674589
Opened 13 years ago
Closed 2 years ago
Panels disconnected from their nsIFrames don't close or respond in OS X
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: rcampbell, Unassigned)
References
Details
Discovered by positioning the web console in a window and trying to close it, xul panels on OS X can become disconnected from their nsIFrame and become zombies. See bug 674562.
Reporter | ||
Updated•13 years ago
|
Comment 1•13 years ago
|
||
I should probably take this. But I won't have time to work on it for a few weeks.
Assignee: nobody → smichaud
Comment 2•13 years ago
|
||
What are the steps to reproduce this bug (pseudo-code for twiddling a xul:panel is fine)?
Reporter | ||
Comment 3•13 years ago
|
||
*twiddle* browser.xul <panel id="my-first-panel" orient="vertical" ignorekeys="true" noautofocus="true" noautohide="true" titlebar="normal" close="true" label="My First Panel!"> <!-- some xul widgetry in here --> </panel> in browser.js, let myfirstpanel = document.getElementById("my-first-panel"); function onpopuphiding(e) { /* do something sufficiently slow that this function will take some * time to complete. * e.g., query and set a bunch of preferences */ } myfirstpanel.addEventListener("popuphiding", onpopuphiding, false); function onpouphidden(e) { /* this will never fire */ } myfirstpanel.addEventListener("popuphidden", onpopuphidden, false); ...
Comment 4•11 years ago
|
||
Is this still happening?
Comment 5•2 years ago
|
||
This is left over from when I was a Mozilla employee. I'll never get back to it.
Assignee: smichaud → nobody
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•