Comment 5 for bug 1783392

We can keep the 300 ms. I will simply disable in in my personal patched version. A search can be started reliably at any time just by pressing ENTER.

The search-as-you-type feature does not fit into the current architecture. In combination with this bug it gets you into trouble if each database query takes >2 sec and freezes the GUI. You need multiple tries with enforced waiting periods in between to correct and finish your intended search, which is unusable in live situations.

Optionally the timeout could be configurable by the user. At least until we have a solution that doesn't cause major usability issues depending on your personal typing speed and habits.