Scott is right. As the world wide web is moving to XHTML, these boolean attributes should be assigned, otherwise the documents aren't valid XML.

Martijn


On 10/13/05, Scott Sauyet <[EMAIL PROTECTED]> wrote:
Nathan Hamblen wrote:
> I need to enable and disable form components in subsequent requests and
> I'm having a hard time with AttributeModifier. It insists on giving
> attributes a value, so I have it put in "TRUE" and it outputs
> 'disabled="TRUE"'. That's not really correct but it works.

Because modern versions of HTML do not allow this attribute minimization
(in order to comply with the XML specs [1]), the norm is to write
"disabled='disabled'".  You can do this with an AttributeModifier.

Good luck,

   -- Scott

[1] http://www.w3.org/TR/xhtml1/diffs.html#h-4.5




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to