Hello this bug is related "18341: window.onunload not fired when the last browser window is being closed" We expected that the handler attached to "window.onunload" gets invoked anytime when a document gets unloaded. This was solved in bug 18341. In the onunload handler we open a new extra window. This new window must stay open during the main window closes. All common browsers (MSIE 5,6,7), (Firefox 2,3) even (Safari f. MacOs) behaves konsistently and guarantee that the window which was opened during onunload is stays on the screen even the main windows has been closed in a meantime. When using Safari for Windows (tested with Safari 4 Developer Preview, 526.12.2) when CLOSING THE LAST BROWSER WINDOW, the Safari opens such new window but then closes it immediately along with the main window - yet before content of the extra window has fully loaded and processed. Note: Even the scenario may look strange for you - we use the window.onuload and the extra window to perform reasonable actions (to notify backend servers about to close backend sessions when the user left the browser), so it is not about just annoying popups/windows, but have strong real and valid usecase. I put the severity to Critical as it is almost a blocker for our applications / session handling.
Created attachment 22460 [details] Sample aaplication showing the bug Start in Safari 4 on Windows and read the descriptionin the HTML file. Summary just close the window and a new window should be open and should stay open.
This sounds very much like a Safari bug rather than a WebKit bug.
(In reply to comment #2) > This sounds very much like a Safari bug rather than a WebKit bug. Agreed.
<rdar://problem/6100327>
As this is likely a Safari bug rather than a WebKit bug, it should be filed with Apple at <http://bugreport.apple.com/>. This bug report should be closed as INVALID per our processes for handling non-WebKit bug reports in Bugzilla.
(In reply to comment #5) > As this is likely a Safari bug rather than a WebKit bug, it should be filed > with Apple at <http://bugreport.apple.com/>. This bug report should be closed > as INVALID per our processes for handling non-WebKit bug reports in Bugzilla. > Done.