Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.7Beta1
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
Description
Interaction between programmer and tester, about the selectInputText component:
P: What happens when there are several entries with the same label? Like selecting users from a list, who happen to have the same name. Will SelectInputText.getSelectItem() give the correct one (maybe their ages differ, so you can easily debug if it's the right one), or will the first entry, or the last entry be the selected one?
T: The last entry gets selected
If you manually type in the label, then it makes sense to have a policy of one of { first / last / undefined / null } to be returned from SelectInputText.getSelectItem(). But, if you actually select it from the list, then instead of submitting the label back to the server, the index should be sent, so that the exactly correct entry could be returned from SelectInputText.getSelectItem().
P: What happens when there are several entries with the same label? Like selecting users from a list, who happen to have the same name. Will SelectInputText.getSelectItem() give the correct one (maybe their ages differ, so you can easily debug if it's the right one), or will the first entry, or the last entry be the selected one?
T: The last entry gets selected
If you manually type in the label, then it makes sense to have a policy of one of { first / last / undefined / null } to be returned from SelectInputText.getSelectItem(). But, if you actually select it from the list, then instead of submitting the label back to the server, the index should be sent, so that the exactly correct entry could be returned from SelectInputText.getSelectItem().
Issue Links
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Fixed by
ICE-1993.