> -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 10:32 AM > To: Struts Developers List > Subject: RE: LabelTag
> backwards compatibility in this way). The W3C spec for <input> is the > about the worst example of a spec definition that I've never > seen, because > many of the specified elements are relevant for only some of the input > subtypes, and the relationships are not always clearly > defined. We'd just > end up with a single tag that had 100 or so optional > attirbutes, with no > clue to the poor user about which ones are relevant for which uses. For an example of this, consider type "hidden". The HTML 4.01 spec defines several attributes of the "input" element which really are only relevant to elements which take visible space on the screen. The specification doesn't specify (somewhat understandably) that concrete "subclasses" of input shouldn't use certain attributes, so as a result the Struts implementation of the "html:hidden" tag implements several attributes that are only there to provide compliance to the specification, but no useful value. If the specification allocated responsibilities to these elements more rationally, the "input" element would have been divided into more than one real element. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
