[ https://issues.apache.org/jira/browse/WICKET-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791494#comment-13791494 ]
Marek Ĺ abo edited comment on WICKET-5101 at 10/10/13 1:39 PM: -------------------------------------------------------------- Hello, what's the current status of this ticket? The patch doesn't seem to be applied in the Wicket 6 master. Does the problem still exist in latest versions? We currently use the snipepts from the patch and we have same issue as WICKET-4695 (undefined win.current inside the deferred function in IE8). Thanks was (Author: zeratul): Hello, what's the current status of this ticket? The patch doesn't seem to be applied in the Wicket 6 master. Does the problem still exist in latest versions? Thanks > 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-5101.patch, > 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 was sent by Atlassian JIRA (v6.1#6144)