[
https://issues.apache.org/jira/browse/WICKET-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608916#comment-13608916
]
Andrea Del Bene commented on WICKET-5101:
-----------------------------------------
@Artem
As you pointed out, we have a synchronization problem due to setTimeout. The
second form is built without waiting for the first to be destroyed.
@Martin
The comment inside function Wicket.Window.close from modal.js says that we can
not directly close the window and we must use setTimeOut. Do you know what's
wrong with directly closing the modal window?
> 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
