When a new test case step requires a test object, searching the Test Object Input dialog is incredibly slow when typing.
This slow response is caused by each keystroke filtering the objects.
There should be an option to set a minimum length or disable the search-as-you-type feature.
Yes I completely agree, as a solution there could be a timeout of .5sec used on keyUp that clears the timeout with each new keyUp, that way it only runs after user has completed typing.