This content has been marked as final.
Show 8 replies
-
1. Re: <rich:select> behavior
michpetrov Jan 11, 2016 6:57 AM (in response to yudhirb)I wonder, if you use duplicate labels, how would the user know which one to choose? That said, this should be fixed in current version (4.5.12)
-
2. Re: <rich:select> behavior
yudhirb Jan 21, 2016 2:34 AM (in response to michpetrov)We changed the version to 4.5.12 but still the issue exists.
Has it been fixed?
-
3. Re: <rich:select> behavior
michpetrov Jan 21, 2016 7:07 AM (in response to yudhirb)Right, that was a different issue. I'll take a look at it, though the far easier option is not to use duplicate labels.
-
4. Re: <rich:select> behavior
yudhirb Jan 27, 2016 12:16 AM (in response to michpetrov)Its the functional requirement. We can't avoid the use of duplicate labels.
-
5. Re: <rich:select> behavior
michpetrov Jan 27, 2016 4:17 AM (in response to yudhirb)That sounds like something that would be very confusing to users, how do you tell between two options with the same label if the label is that all you see?
-
6. Re: <rich:select> behavior
yudhirb Jan 27, 2016 4:41 AM (in response to michpetrov)We use tooltips for that purpose. We have a business requirement. So, can't do much on that side.
-
7. Re: <rich:select> behavior
michpetrov Jan 27, 2016 5:15 AM (in response to yudhirb)Alright, can you file a bug in JIRA? JBoss Issue Tracker
-
8. Re: <rich:select> behavior
yudhirb Jan 27, 2016 5:23 AM (in response to michpetrov)ok. I will do that.