Closed Bug 722667 Opened 13 years ago Closed 3 months ago

XULRunner on Windows does not handle the unload event when the process is killed.

Categories

(Core :: General, defect)

9 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: abryson, Unassigned)

Details

User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET4.0C; .NET4.0E) Steps to reproduce: A simple XUL applicaiton consisting of only a <window> will not fire the wired-up unload event when xulrunner.exe is killed via task manager. This did work in XULRunner version 1.9.2.9, but upon upgrading to 9.0.1 it no longer works. The single XUL file contents are: <?xml version="1.0"?> <?xml-stylesheet href="chrome://global/skin/" type="text/css"?> <window xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" id="window" title="Title" hidechrome="false" sizemode="maximized" onunload="alert('fired unload');"> </window> Actual results: The alert does not show when I kill xulrunner.exe from task manager. The process simply dies. The alert is shown when: 1. I click the X [close] on the window chrome to close the window. 2. Use Alt + F4. Expected results: My application requires code execution when the window is being unloaded, including if it is being killed by the OS. As I said, this did work in an old version of XULRunner, but does not work in 9.0.1 or 10.0b6.
Severity: normal → S3

xulrunner isn't a thing anymore

Status: UNCONFIRMED → RESOLVED
Closed: 3 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.