267492 - XMLHttpRequest onload event is not called if a dialog closes itself and lets the opener do the request

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Michali Sarris]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041102 Firefox/1.0RC2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041102 Firefox/1.0RC2

The XMLHttpRequest onload event is not called if a dialog window makes the
opened window make a request and after that closes itself. The event will be
called however when: 1. the dialog stays open 2. an alert() is called after the
send() operation.

The provided url demonstates this. On the start window is a button wich makes
the dialog open. On the dialog you will find 4 buttons with different
combinations of calls. The event wil be called in 3 of 4 possiblilities. The
only time the event wont be triggerd is when no alert() statement is used and
the dialog is closed.

Reproducible: Always
Steps to Reproduce:
1. Open the dialog
2. Press the second button

Actual Results:  
The dialog closes and nothing else.

Expected Results:  
The dialog should have closed and an alert should have been triggerd in the
onload event.

Comment 1

[Michali Sarris]

Attachment: The window that opens the dialog and does the request.

Comment 2

[Michali Sarris]

Attachment: The dialog that triggers the request in the opener window (win.xul).

Comment 3

[Boris Zbarsky [:bzbarsky]]

Attachment: The window that opens the dialog and does the request (pointed at the dialog).

Comment 4

[Boris Zbarsky [:bzbarsky]]

I'm pretty sure that the XMLHttpRequest is added to the loadgroup of the window
the code is called from (the dialog, in this case).  When that window is closed,
all associated network activity, including the XMLHttpRequest, is cancelled.

I'm also pretty sure we already have bugs on this.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.