[
https://issues.apache.org/jira/browse/WICKET-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500414#comment-13500414
]
German Morales commented on WICKET-1826:
----------------------------------------
Hi Stijn,
it's nice to see someone finally interested in fixing this bug.
I hope you didn't lose much time with it, but what you propose...
>replaced it's first line:
>getForm().getRootForm().onFormSubmitted();
>with:
>getForm().onFormSubmitted();
is exactly what i've already proposed back on Sep/08 (see the attached
modalwindowform.jar, MyAjaxSubmitLink.java, line 41.
> Forms + ModalWindow + AjaxSubmitLink + FormComponent#isInputNullable
> --------------------------------------------------------------------
>
> Key: WICKET-1826
> URL: https://issues.apache.org/jira/browse/WICKET-1826
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.3.3
> Reporter: German Morales
> Priority: Minor
> Attachments: bug.zip, modalwindowform.jar, modalwindowform.jar,
> WICKET-1826.patch
>
>
> Submiting a form which is inside a ModalWindow, wicket javascript sends only
> the information for the modal window's form, but not for the root form of the
> page (because ModalWindow hangs its own div at body level).
> On Wicket server side, the form processing is done for the root form, which
> calls inputChanged for all the components in the page, but the javascript
> side didn't send the information for them, and then some of them go wrong.
> That happens to FormComponents which have isInputNullable in true.
> More description and proposed solutions in the (to be) attached quickstart
> project.
--
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
