Page History

...

However for the output to be HTML compliant, there must be a means to remove Wicket-specific information not relevant for the client browser from markup. XHTML shouldn't be a problem because all wicket-specific information is cleanly separated by using the wicket namespace, but not all browsers support XHTML well enough not to stumble over them.

The solution is to call getMarkupSettings().setStripWicketTags(true) in the init method of your Application class. (Use getSettings().setStripWicketTags(true) for Wicket 1.1 and earlier.) This will remove from output all Wicket tags with Wicket namespace. That is, your output should not contain any tag like <wicket:panel> any more. It is off by default (not removing the tag). As these tags are not relevant for the client browser at all, I'd allways always keep it off during development and switch it on (remove them) for production sites.

...