On 8/15/05, Seth Ladd <[EMAIL PROTECTED]> wrote: > On 8/14/05, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > > > fixed in head. > > Great! Can you explain the relationship between XHTML, HTML, and > rendering components? What is The Wicket Way? Is it configurable? > Or is the idea to subclass/override methods that output (X)HTML > content when you want it to change? > > I'm perfectly fine w/ everything outputting XHTML, but wondering how > the decision (if any) is made. >
Only very few components, like RadioChoice, have (x)html code inline (in java) which should be (x)html and html compliant, assuming that in these few cases compatibility for both is possible. Everything else is up to the designer creating the markup file. We do not test the markup generated for (x)html compatitbility; there are plenty of tools out there. Juergen ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
