Shahin Alborz – EPiServer & ASP.NET developer

Yesterday I noticed very odd behaviour in an editor interface using a javascript showModalDialog function.

After a lot of testing and pulling my hair, I came to the conclusion that it’s a bug in Google Chrome (tested in Chrome version 10) which cause the return value to be unreadable from the modal window, after a redirection of any kind (reload, post, etc) has occurred.

When the content of the modal window first loads, there’s no problem at all. After a post inside the window has been made, or for instance a change page link has been clicked, the connection to the parent window seems to be broken for ever and ever. The returnValue will be “undefined” until the window is closed and a new modal dialog has been opened.

I made a testpage to recreate this bug in Google Chrome, test it here:
modalDialogTest (opens in new tab/window)

This entry was posted on Friday, March 18th, 2011 and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.