[jira] [Resolved] (WICKET-4331) AJAXDownload from ModalWindow breaks Ajax on base page

["Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4331.
-------------------------------------

    Resolution: Not A Problem

The problem was in AJAXDownload.
With the immediate call to "window.location.href=url" it didn't allow Wicket to finish its job (releasing the lock on the Ajax channel).

By changing line 44 to 
target.appendJavaScript("setTimeout(\"window.location.href='" + url + "'\", 100);");
all is fine.
                
> AJAXDownload from ModalWindow breaks Ajax on base page
> ------------------------------------------------------
>
>                 Key: WICKET-4331
>                 URL: https://issues.apache.org/jira/browse/WICKET-4331
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.3
>         Environment: Windows 7 Pro 64bit, Java 1.6.0_30, Maven 3.0.3, Google Chrome 17 (dev channel)
> Mac OS 10.5.8, Java 1.6.0_26, Maven 3.0.3, Google Chrome 17 (dev channel)
>            Reporter: heapifyman
>              Labels: ajax, download, modal, wicket, window
>         Attachments: myproject.zip
>
>
> Following the approach described here https://cwiki.apache.org/WICKET/ajax-update-and-file-download-in-one-blow.html I implemented downloading a PDF from a ModalWindow. The page from where the ModalWindow is opened, also contains other Ajax functionality (like the AjaxLinks, etc.)
> After the file is downloaded and the ModalWindow is closed all my Ajax stuff on the base page, from which the ModalWindow was opened, are not working anymore. Only when I reload the page, the Ajax stuff is working again.
> This happens in Google Chrome but not in Safari and Firefox. Not sure if it's a Wicket or a Chrome specific problem.
> A quickstart example showing the problem is attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira