Hello,

I have exactly the same problem as described here. The only reason is that I need to execute server-side code when close button is clicked.

Solution is needed urgently, because the project is needed to be presented to public audience next week. Any help will be appreciated! 

 Just found a solution : user server control and register close script in the event handler just like this:

ScriptManager.RegisterStartupScript(this, sender.GetType(), "Close", "window.close()", true);

PS It's a pity that AJAX has such bugs. 

PPS I would like to know if there is a fix from Microsoft for this bug. 

Hi,

Ajax doesn't have such bug, this is a browser bug and bad code.

Putting window.close in the onclick of a submit button is bad, because you break the async postback: the browser cannot handle the situation: browser bug.

If you want to close without server side code, use a simple input element (type=button), you don't need an asp:button for this.

If you want some server side code before closing your window, RegisterStartupScript is the (easiest) way, as you find out.

Strange thing is that this is not documented anywhere. And it is regularly reproduced on the third (not the first...) request. But ok with this.

 What is the right (smartest) way to do this?

PS And I do not really understand why this is browser that cannot process async request after it is closed. As I understand the instance of the browser is destroyed. Thus the result is not processed at all. Why should it be a problem?
 

 I would stay with registerstartupscript, but you can use other events for closing the window (endRequest Event and a flag which indicates that the window should be closed): ASP.NET AJAX Client Life-Cycle Events

Me too. The reason is that it is not obvious and there should be some kind of a filter in endRequest.

Anyway thanks for ideas!