To disable wicket-tags in the generated HTML (in Wicket 1.1.1), you add
in the init()-method of your webapplication the following line:
getSettings().setStripWicketTags(true);
For Wicket 1.2 this line will be:
getMarkupSettings().setStripWicketTags(true);
BTW, as I understood from previous entries in this mailing list, as of
Opera 9 (now in beta), Opera no longer is upset with the wicket-tags.
Regards,
Dave
Johannes Fahrenkrug wrote:
Hi,
It took me a while to track down why Opera makes my Wicket application
look like crap.
Here's why:
when you use a css class like
td.someclass
and apply that class to a <td> tag within a table that is surrounded
by <wicket:border> tags, Opera doesn't apply the CSS class to the td
tag. If you define a general CSS class like
.someclass
it works (or when there are no <wicket:border> tags.
Everything is fine when using Firefox, Safari or even IE.
My question is: Can I somehow keep the <wicket:border> tags from
showing up in the rendered markup?
I'm using wicket-1.1.1.
I've attached a file that demonstrates the problem (like I said: only
happens with Opera).
Cheers,
Johannes
------------------------------------------------------------------------
Test1 Test2
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
