I’m looking for a way to adjust the incrementalSearch behavior so that it starts searching the moment a key is pressed rather than waiting for the user to stop typing. This is distinct from the incrementalSearchDelay property which is the delay until the internal search string is reset.
Currently it appears that there’s about a 200-300ms delay after finishing typing before the incremental search will happen. I would instead like each keypress to immediately trigger an incremental search. This is the behavior the browser gives with a <select> element.
Similar behavior can be seen if enabling filterable
and setting filterDelay
to 1
. The list filters instantly upon typing, and the user gets real time feedback whether they have sufficiently narrowed down the list or if they need to type a longer filter string.
I don’t see any property on the API documentation to do what I’m looking for. I’d also settle for being able to add my own keyup event listener and calling a method that will force the incremental search to happen. Any ideas would be helpful. Thanks.