You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Anthony DePalma <fa...@gmail.com> on 2010/07/03 15:36:22 UTC

Modal window form not submitting in Chrome after dependency change?

I seem to be having a strange problem that I believe started happening
possibly after changing wicket versions or cleaning up my
dependencies.

In a nutshell, if I open a modal window with a form in it, and submit
the form via ajax, nothing happens in Google Chrome. I turned on
wicket debug and see this:

INFO: Initiating Ajax POST request on
?x=T6A9Uh08GjZ792nMsL*7MTfnPw6KtS9I-1ZhuquwzdJG*oyNHNd0zliePICU1Am3saa5e9ZQflaJdIqbf8yOScR7bT25REAiT84oJ4mHgQDXPnH5HtlqAJkUfCLruD7PVsEb5JK*6IoielouglZuyAYG0TL8L-o0FLidbtItO8CmCwGScr6sEvv4FB-sOz3n-AD310Ii0TCf9DePnphlLw&random=0.7639111690223217
INFO: Invoking pre-call handler(s)...
INFO: Received ajax response (69 characters)
INFO:
<?xml version="1.0" encoding="UTF-8"?><ajax-response></ajax-response>
INFO: Response parsed. Now invoking steps...
INFO: Response processed successfully.
INFO: Invoking post-call handler(s)...
INFO: refocus last focused component not needed/allowed

The strange thing is if I do the exact same thing in firefox or IE, I
get a healthy response including the panel to replace the form with
and the form updates. For chrome though, something seems to prevent
the ajax-response from coming back. If i close the modal window in
chrome, open it again and submit it, it works fine. But the first
attempt always does nothing and is very frustrating for usability as
there is no feedback that anything went wrong besides the ajax
indicator flashing. Subsequent submits do nothing but return the empty
ajax response unless i close and reopen the window.

And even stranger, the older version of my site works fine in the same
chrome browser, but if I revert my wicket dependencies it doesnt fix
the problem. I am guessing there is something strange about maybe a
non wicket dependency I got rid of, but I still have to mess around
with it. But has anyone seen this kind of behavior before or have a
hint as to how I could debug it?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org