The issue with the current rules is shown with this example. Here we are in an empty field:
Although this is now basically working e.g.:
Now I type G and get:
but I add an r and the list grows.
I think that the list should never grow when you add more characters. This means that I think we must have both 'startsWithand 'includes' matches from the first character. Given that thestartsWith matches are listed before thecontains` matches - this is unlikely to be intrusive.
Controlled here:
Additionally
Change the case-sensitivity rules
If the user enters a string that contains any upper case then test against the case the user has entered. If the user's entry is all lower case then test it case insensitively.
The issue with the current rules is shown with this example. Here we are in an empty field:
Although this is now basically working e.g.:
Now I type
G
and get:but I add an
r
and the list grows.I think that the list should never grow when you add more characters. This means that I think we must have both 'startsWith
and 'includes' matches from the first character. Given that the
startsWithmatches are listed before the
contains` matches - this is unlikely to be intrusive.Controlled here:
Additionally
Change the case-sensitivity rules
If the user enters a string that contains any upper case then test against the case the user has entered. If the user's entry is all lower case then test it case insensitively.