Thanks, I didn't realize this was valid (and even required) for XHTML.
It might be worth a comment in AttributeModifier and elsewhere; I didn't
realize Wicket preferred XHTML markup.
Nathan
Scott Sauyet 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
-------------------------------------------------------
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
