We just discovered that if a Map<String,String> gets passed to a select-tag
where the entry's key/value pair are "<MULTIPLE>"/"<MULTIPLE>" that the
option's value attribute contains "<MULTIPLE>" as one would have expected, but
the body of the option-tag is empty as seen here
<option value="<MULTIPLE>"></option>
There isn't a clean way to scrub this data to eliminate the HTML-brackets under
these test cases and was curious whether there was an undocumented way to get
this to work by setting escape="false" or something of the sorts? I realize we
can iterate the map and do a replace before passing it to the select-tag, but
this isn't ideal for all scenarios because of the business requirements and use
cases. The ideal solution is to be able to present "<MULTIPLE>" as a valid
option in the drop down to accurately map to the customer's stored data.
Thanks
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]