On Thu, 21 Nov 2002, Chen, Gin wrote:
> that makes sense. > but how about including an attributes tag that allows a map of attribute > name/values? > that might be helpful while maintaining the whole "not render any client > specific attributes". One of the main reasons Struts will not support client-specific attributes (like "autocomplete") is that I want to discourage developers from creating applications that depend on non-standardized functionality. Adding a general purpose "attributes" tag would just open that door for that kind of thing, so I would not be in favor of it. The previous suggestion (extend an existing Struts implementation with your own) is the best way to deal with this kind of thing. Then it is *your* application that is explicitly choosing to support non-standard behavior of a particular client. > -Tim Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
