Issues with autofill for database search

[Brawler_1337]

Ever since iMtG updated to include iOS 9 support, the database search bar has added in a context-based list of suggestions for card names. However, I find this feature has been more frustrating than helpful as of late because once you type in the first three letters, the app will automatically fill those letters in once you start deleting letters. For example, say I'm searching for {Abandon Hope}, but I accidentally type in "Abb." I realize my mistake and start deleting to correct the typo. Here, the app will fill in "Abb" again, and I'll be searching for "Abbandon Hope" even though I deleted down to "Ab" and started typing "andon Hope." What's more annoying, the app keeps doing this unless I delete and correct the typo very fast.

What's going on? I can't imagine this is intentional. Is it a bug?

[ELLERfeller]

I've had the same problem

[Piotr]

If you don't like it, must be a bug then?

[Piotr]

No it is actually a feature. Go to Main Menu -> Settings & Tools -> LOOK AND FEEL -> Background Search to switch it off.

Very fast is relative. How fast are you in comparison to this kid? https://www.youtube.com/watch?v=KIMb2pWAgm4

Do you want a speed slider there?

[Brawler_1337]

No it is actually a feature. Go to Main Menu -> Settings & Tools -> LOOK AND FEEL -> Background Search to switch it off.

Very fast is relative. How fast are you in comparison to this kid? https://www.youtube.com/watch?v=KIMb2pWAgm4

Do you want a speed slider there?

I like the concept of background searching since it makes querying easier, which is a big plus for user experience. I think a speed slider might help. Either that or a more prominent "clear search" button, since that's the most effective way of dealing with this right now.

I am also a decently fast typist. It's just that the background search feature requires me to hit the backspace key a few more times than I'd normally expect, which adds a little time to quick searches.

[Piotr]

Ok, your feedback is clear and precise, therefore what you ask for should be fixed in 5.16.0 update, thanks!