Currently, autocomplete is completely case-sensitive; it will ignore paths that don't match the case of anything in it. This is really awkward when, for example, you have three paths that all start with "Osmose" and you type in "os" as the fragment and attempt to autocomplete.
The intended behavior is that any text already in the path is treated as case-insensitive when matching, but any new letters it is filling in should be treated as case sensitive, so that autocompleting will not complete beyond the difference in case.
Currently, autocomplete is completely case-sensitive; it will ignore paths that don't match the case of anything in it. This is really awkward when, for example, you have three paths that all start with "Osmose" and you type in "os" as the fragment and attempt to autocomplete.
The intended behavior is that any text already in the path is treated as case-insensitive when matching, but any new letters it is filling in should be treated as case sensitive, so that autocompleting will not complete beyond the difference in case.