Re: Multi-tabs and back-button support 1.5.2
I have now created an issue on jira with the actual problems described above. https://issues.apache.org/jira/browse/WICKET-4182 https://issues.apache.org/jira/browse/WICKET-4182 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Multi-tabs-and-back-button-support-1-5-2-tp3943445p3947091.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
Re: Multi-tabs and back-button support 1.5.2
I would actually like to accept the data from both tabs as long as they are valid. The same effect should be available on back-button and changing values. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Multi-tabs-and-back-button-support-1-5-2-tp3943445p3943856.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
Multi-tabs and back-button support 1.5.2
We are developing an application with forms and currently using wicket 1.4.18. There are primarily two issues that we are struggeling with when upgrading to wicket 1.5.2. Let's say we open Page A in two tabs, first Tab1 and then Tab2. If we fill the form in Tab1 and submit it will be valid data, but they are not stored on our models. However, if we fill in form in Tab2 they are stored since this tab has a higher version number than Tab1. More or less the same issue exists when using back-button. Open PageA, fill in the form and submit. Use back-button and change values and submit. The new values are not stored on the models. In our case it would have been better if the version number increased when using the back-button. Is it supposed to work in 1.5.2, and are there some special settings one must be aware of? Charlie
