Closed
Bug 12077
Opened 25 years ago
Closed 25 years ago
Bringing up a Javascript alert() from a dialog leads to lockup.
Categories
(Core Graveyard :: Embedding: APIs, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
M10
People
(Reporter: slogan, Assigned: danm.moz)
References
()
Details
Bringing up a xul or html dialog which has a button that, when clicked, displays a javascript alert() will lead to a hang when you try doing a window.close() on the window/dialog that was used to launch the alert (the alert itself dimisses fine). To reproduce, bring up resource:/res/samples/dexopenchrome.xul, click on the HTML dialog button (no need to select any checkboxes, defaults work fine), click on the Show Alert button at the bottom of the dialog, dismiss the alert, then click on the OK button in the html dialog to dimiss it. But, it hangs. Closing the dialog using the Windows close box does work, however. This is a dogfood blocker.
Status: NEW → ASSIGNED
Whiteboard: fix in hand; waiting for !%%!#$ tree to open
Target Milestone: M10
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: fix in hand; waiting for !%%!#$ tree to open
Return of son of refcounting problem. Would that all refcounting mistakes were so visible.
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•