This problem is only present when using Safari (Chrome, FF, and IE work fine.
Specifically I found this in Safari 5 on Windows 7). Also, only when using
ajax buttons for both forms submittal, rather than a vanilla form submission
for the second form.
I have two forms on a single page, the second one isn't visible on page
load. When you submit the first form I change the visibility so that the
first form is invisible and the second is visible:
pTarget.addComponent(_form1.setVisible(false));
pTarget.addComponent(_form2.setVisible(true));
In Safari only this result in neither form rendered after submission.
Switching the order in form1's onSubmit() rectifies the immediate problem:
pTarget.addComponent(_form2.setVisible(true));
pTarget.addComponent(_form1.setVisible(false));
However, now when you submit the second form, the client hangs on INFO:
Response parsed. Now invoking steps... It never gets to the submit button's
onsubmit(). It gets stuck while processing steps in the processNext()
function of Wicket.FunctionsExecuter in wicket-ajax.js and so it never calls
the final success function, hence the hang.
As a work around, you can change the first form's onSubmit() to this:
pTarget.addComponent(_form2.setVisible(true));
pTarget.addComponent(_form1.add(new SimpleAttributeModifier(style,
visibility:hidden)));
Is there a real fix for this? It seems like there may be a bug in how
wicket-ajax.js handles Safari. Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Safari-hangs-on-ajax-form-submit-tp3713539p3713539.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org