[ 
https://issues.apache.org/jira/browse/WICKET-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645555#comment-13645555
 ] 

Andrea Del Bene commented on WICKET-5101:
-----------------------------------------

Well, JQuery deferred can actually solve this issue and It can be also applied 
to 6.x branch. I've attached a patch with a possible solution. However I would 
also consider to remove setTimeOut from function Wicket.Window.close and test 
it with all main browser. This solution would reduce the complexity of modal.js 
instead of increasing it.
                
> Could not open second modal window after closing first
> ------------------------------------------------------
>
>                 Key: WICKET-5101
>                 URL: https://issues.apache.org/jira/browse/WICKET-5101
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.6.0
>            Reporter: Artem Morozov
>              Labels: ajax, modal
>         Attachments: modalFormClose.zip, wicket-ajax-response.js
>
>
> Precondition: first modal window is opened. 
> It has ajax submit form inside.
> After submitting form inside modal I want to open another modal with another 
> content.
> I debugged wicket ajax response and found, 
> that script, witch should close first window, closes second instead.
> I attached wicket-ajax-response.js to demonstrate the problem.
> wicket ajax engine correct runs those two functions, but 
> "win.current.close();" at line 16
> actually closes second window, opened at line 40.
> See also
> https://issues.apache.org/jira/browse/WICKET-1576

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to