[ http://issues.apache.org/struts/browse/STR-1195?page=comments#action_38916 ] Paul Benedict commented on STR-1195: ------------------------------------
I think it's perfectly acceptable to pluck out one value for a special case. 99% backwards compatibility is good enough, imo. > [taglib] "multiple" attribute on select tag should not render when false > ------------------------------------------------------------------------ > > Key: STR-1195 > URL: http://issues.apache.org/struts/browse/STR-1195 > Project: Struts 1 > Issue Type: Improvement > Components: Taglibs > Affects Versions: Future > Environment: Operating System: other > Platform: Other > Reporter: Justin Ashworth > Assigned To: Struts Developers > Priority: Minor > Fix For: Future > > > There is currently no value that can be passed to the "multiple" attribute of > the <html:select> tag that would indicate you want to render the component as > a > single select - not even false. This would be useful in the case where you > have a generic JSP that, depending on a value retrieved from some bean, may > render a single or multiple select. > Maximum backwards compatibility could be achieved if the only value that > would > render a single select is "false". Chances are that nobody is currently > using > the value "false" to render a multiple select. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
