Panels disconnected from their nsIFrames don't close or respond in OS X

NEW
Assigned to

Status

()

Core
Widget: Cocoa
7 years ago
4 years ago

People

(Reporter: rc, Assigned: smichaud)

Tracking

Trunk
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
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

7 years ago
Blocks: 674351, 674562
(Assignee)

Comment 1

7 years ago
I should probably take this.  But I won't have time to work on it for a few weeks.
Assignee: nobody → smichaud
What are the steps to reproduce this bug (pseudo-code for twiddling a xul:panel is fine)?
(Reporter)

Comment 3

7 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);

...
(Reporter)

Updated

6 years ago
Blocks: 702707
(Assignee)

Comment 4

4 years ago
Is this still happening?
You need to log in before you can comment on or make changes to this bug.