and I think we currently modify only attributes of wicket tags (which have wicket:id or <wicket:xxx>). We do not modify all other tags nor attributes. IMO it can be very confusing to users why some tags/attributes are changed and others are not.
Juergen On 9/6/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > As fas as I know this was the reason. All XHTML tags and attributes > are lowercase and yes, they are case sensitive. IMO we should not > modify the case the names to make it compliant. It should be the > designers task. > > Juergen > > On 9/6/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > I think this is done to be 'xhtml' compliant, in that we don't expect > > people to introduce their own attributes. The xhtml provided attributes are > > all lower case to my knowledge, so that may be the reasoning. > > > > Martijn > > > > > > 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
