https://github.com/apache/wicket/blob/master/wicket-examples/src/main/java/org/apache/wicket/examples/ajax/builtin/modal/ModalContent1Page.java?source=c#L91 does something similar. It uses alert() additionally. You can test it at http://www.wicket-library.com/wicket-examples-6.0.x/ajax/modal-window?0 (Show dialog with a page, the inner modal).
I'm not sure why it tries to leave the page in your case. You can also hide the "x" button with CSS rule, so your user won't be able to click it. On Wed, Dec 11, 2013 at 10:56 AM, J.K. Baltzersen <jornb...@pvv.org> wrote: > I am not submitting a form. There is no submit button. I am invoking the > modal window upon wait for load of the page to complete (non-Ajax). > > However, the setCloseButtonCallback includes an onCloseButtonClicked > defined > and declared with an AjaxRequestTarget parameter. > > If I remove the overridden callback, I don't have that problem, but then > the > user may close the window at will and hence be able to do edit before the > page is completely loaded, which undermines the purpose of the dialog box. > > > Martin Grigorov-4 wrote > > Hi, > > > > Do you use *Ajax* button to submit the form ? > > If you use normal (non-Ajax) submit button then you will leave the page. > > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/user-activity-disabled-during-page-load-tp4662891p4662910.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 > >
