Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-11 Thread Pierre-Yves Saumont
I finally find what caused the problem: I knew that for the example to work as standalone, one must call setOutputMarkup(true) on the ListView container. What I did not know is that if the example is embeded in an Ajax TabbedPanel, the Form used to update the ListView must also have

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-11 Thread Johan Compagner
can wicket do something to improve this?On 8/11/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote: I finally find what caused the problem: I knew that for the example towork as standalone, one must call setOutputMarkup(true) on the ListViewcontainer. What I did not know is that if the example is

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-11 Thread Igor Vaynberg
yes, we can ditch : as the default separator and use something else like an underscore.-IgorOn 8/11/06, Johan Compagner [EMAIL PROTECTED] wrote:can wicket do something to improve this? On 8/11/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote: I finally find what caused the problem: I knew that

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Pierre-Yves Saumont
Hello, After spending the night testing, it appears that there are two different problems : 1) The Ajax handler - onSubmit(AjaxRequestTarget target, Form form) - is not called and Wicket default to onSubmit() if is is present. I can't see why Ajax does not work for this form, since it works

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Johan Compagner
do you have a simple test case in a quickstart project?On 8/10/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote: Hello,After spending the night testing, it appears that there are twodifferent problems : 1) The Ajax handler - onSubmit(AjaxRequestTarget target, Form form) - isnot called and Wicket

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Pierre-Yves Saumont
I eventually could not reproduce the problem in a test case. However, I have been able (??) to produce another problem of the same kind, ie something that does not work the same in IE6 and Firefox. In fact, it works fine in FireFox and produces an error in IE6. The example is a ListView that

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Igor Vaynberg
you cannot update listview directly because a) listview itself has no markup - it lets the children use its markupb) you cannot update tr/tbody/etc tags via outerhtml which is what we do and when you try you get the very helpful runtime error you have to create a markupcontainer around the

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Pierre-Yves Saumont
you cannot update listview directly because a) listview itself has no markup - it lets the children use its markup I know this because I made some research on the list archive and found one of your post where you explained this problem ;-) b) you cannot update tr/tbody/etc tags via outerhtml

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Igor Vaynberg
b) you cannot update tr/tbody/etc tags via outerhtml which is what we do and when you try you get the very helpful runtime error I do not get any error in Firefox although I update tbody !not all browsers are born equal. have you tried safari? opera? konqueror? :)-Igor

Re: [Wicket-user] ListView updated twice in IE6 (Was : Ajax Submit default to Non Ajax Submit ?)

2006-08-10 Thread Pierre-Yves Saumont
I am sorry, I just hit reply and although sometimes it goes to the list, sometimes not :-( I tried to use the enclosing tab as the target, as well as the panel that was used in the standalone version. In either case, absolutely nothing happens. And nothing is displayed in the Ajax Debug