yes i just read that in a jira issue :) but in my example it doesn't ... will check it
On Thu, Feb 16, 2012 at 20:20, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > the whole idea of putting the modal into a wicket form is that forms > inside the modal should change their form tags to divs because they > see they are inside another form... > > -igor > > On Thu, Feb 16, 2012 at 11:16 AM, Johan Compagner <jcompag...@gmail.com> > wrote: > > here: > > > > > http://wicket.apache.org/apidocs/1.5/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.html > > > > we say > > > > "If you want to use form in modal window component make sure that you put > > the modal window itself in another form (nesting forms is legal in > Wicket) > > and that the form on modal window is submitted before the window get > > closed." > > > > problem is that this is illegal in the browser. > > And chrome some if i push through ajax new content in the modal dialog > that > > has that form > > completely removes the form from the resulting component tree.. > > > > I guess this is because the modal dialog generates a form tag itself, and > > then also a form tag is generated in the content of the modal dialog > itself > > and chrome just filters that out? > > Weird thing is that chrome doesn't do that when you do a full page > > refresh... > > > > johan >
