Skip to:
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Refer to the following DS instance for the purposes of illustration:
https://sh2testsp1.iay.org.uk/Shibboleth.sso/DS
Symptoms: Type "b" into the search field. Nothing happens. Now append "r" to the search string so that "br" is entered into the search field. Again, nothing happens. Type a third character so that the string "bra" is entered into the search field. This time, a list of 12 IdPs is displayed. Delete the "a" character and append the character "b" so that "brb" is entered into the search field. No match.
I naturally expect every keystroke to modify the UI in some way. I don't think this is an unreasonable expectation, but clearly the application doesn't work this way, so presumably there's some good reason for this.
Some ideas:
Every input character should elicit a response, that is, every keystroke should modify the UI in some way
Let N be a configuration parameter where N is the maximum number of displayed IdPs
For a given search string, let M be the # of matches. If M > N , display the first N matches and the string "P more matches..." at the bottom of the list, where P = M - N
In lieu of the previous (advanced) behavior, display the string "too many matches" (although clearly this is less desirable)
For a given search string, if M = 0 , display the string "no matches"
In the list of displayed IdPs, highlight the search characters (which I realize are not necessarily contiguous characters)