I think we originally used this to be sure the wicket-id attribute wasn't messed up. I'm +1 for removing the case cast again, though our error reporting should clearly indicate that case differences could be a possible cause of when components were not found.
Eelco On 9/6/05, Cameron Braid <[EMAIL PROTECTED]> wrote: > > > > I am adding an AttributeModifier to a component, using a camel case > attribute name. > > > > When the HTML is rendered, the attribute name is all lowercase. > > > > Is this the intended behaviour ? > > > > Can the attribute name case be preserved ? > > > > This is important in XHTML where attribute names are case sensitive. > > > > Cameron. ------------------------------------------------------- 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-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
