[
https://issues.apache.org/jira/browse/WICKET-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596327#action_12596327
]
Matej Knopp commented on WICKET-1625:
-------------------------------------
Check if your markup is valid. It looks like you've a block element inside
inline element or something like that. That will work on normal requests, but
will break during ajax request. Also if you have modal window with panel and
form in it, make sure you put the actual modal window in form as well. Also
that you use the latest 1.3 version.
> ajax update brakes Form in ModalWindow
> --------------------------------------
>
> Key: WICKET-1625
> URL: https://issues.apache.org/jira/browse/WICKET-1625
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.3.3
> Environment: tested in IE7, FF2 and FF3
> Reporter: david r.
> Priority: Critical
>
> When a Form contained by a ModalWindow is updated via AJAX (for example to
> perform field validation), the AJAX response is correct (the full correct
> form is in the response) but the final HTML code (after the Ajax update) is
> erroneous.
> A consequence is that a second attempt to submit the same Form via AJAX
> generates a JavaScript error: wicket-ajax.js, line 456, "element has no
> properties".
> In other words, "element" is NULL at this point.
> A possible reason for this:
> By looking at the HTML with Firebug, one can see that before the first AJAX
> call, the page looks like <html>...<form
> id="bar"><formfields>...</formfields></form></html> and after the request
> (i.e. after the AJAX update of the Form) the code is
> <html>...<formfields>...</formfields></html> : the "form" tags disappeared
> from the HTML code...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
