On Wed, Mar 17, 2010 at 10:28 AM, Martin Grigorov 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 browsers rendered
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 wil
---------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
> -
> To unsubscribe, e-
Shameless plug (but it has helped our company's HTML considerably):
You could consider using the html validator filter for that
(http://github.com/dashorst/wicket-stuff-markup-validator)
Martijn
On Tue, Mar 16, 2010 at 6:10 PM, Igor Vaynberg wrote:
> i have seen that happen when you have invali
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 wrote:
> Hi,
>
> I'm experiencing a weird problem with Wicket Ajax in Firefox 3.6 (I
> didn'
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 TextField textField = new TextField("text", new
PropertyModel(this, "text"));
textField.setOutputMarkupId(true);
textField.setOutputMarkupPlaceho
