Re: Wicket.replaceOuterHtml problems in Gecko

2010-03-17 Thread martin-g
/Wicket.replaceOuterHtml-problems-in-Gecko-tp27921435p27928225.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h

Re: Wicket.replaceOuterHtml problems in Gecko

2010-03-17 Thread Martin Grigorov
Hi Martijn, I have two problems with your filter: 1) The main problem is that our pages does not have XHTML doctype. The pages are XML well formed but this is not enough. I tried once to set this doctype and the browsers rendered them in a very funny (and broken) way. The HTML and probably CSS

Re: Wicket.replaceOuterHtml problems in Gecko

2010-03-17 Thread Martijn Dashorst
On Wed, Mar 17, 2010 at 10:28 AM, Martin Grigorov mcgreg...@e-card.bg wrote: Hi Martijn, I have two problems with your filter: 1) The main problem is that our pages does not have XHTML doctype. The pages are XML well formed but this is not enough. I tried once to set this doctype and the

Wicket.replaceOuterHtml problems in Gecko

2010-03-16 Thread Martin Grigorov
Hi, I'm experiencing a weird problem with Wicket Ajax in Firefox 3.6 (I didn't test in older versions of FF). Basically my code looks like this: final TextFieldString textField = new TextFieldString(text, new PropertyModelString(this, text)); textField.setOutputMarkupId(true);

Re: Wicket.replaceOuterHtml problems in Gecko

2010-03-16 Thread Igor Vaynberg
i have seen that happen when you have invalid markup. like a div inside a span, or a div directly inside a tr. check your page for stuff like that. -igor On Tue, Mar 16, 2010 at 10:02 AM, Martin Grigorov mcgreg...@e-card.bg wrote: Hi, I'm experiencing a weird problem with Wicket Ajax in