Closed mscheper closed 5 years ago
This is probably due to instant search being enabled by default. It starts searching upon the first character being typed. This can be disabled in the extension options. In terms of performance, I haven't really figured out a way to make it faster. If you have some ideas I would love to take a pull request.
When I use a keyboard shortcut to open Chrome Regex Search and immediately start typing a query string, the first few characters in my query string are lost. Sometimes, the first character or two end up in a text field on the web page, even though I type them after the keyboard shortcut. I don't mind that the dialogue takes a little while to appear (a few hundred milliseconds), but I'd map this extension to Ctrl+F if none of the characters I typed got lost.
Chrome 65 under Linux Mint 18.1 64b (Cinnamon 3.2.7) on an admittedly old laptop (dual core i7 @ 2.90GHz).