Start autocomplete search after n chars entered
See original GitHub issueThe autocomplete should only start sending requests once there’s more than n
characters because the results for a single char aren’t that useful.
In the past typical values for n
would be 2-3 chars - it’ll make sense to make this configurable so it’s easily tweaked. Let’s start with 2 chars and go from there.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Show autocomplete only after 3 entered chars in <datalist ...
Here is a way to do it: removing the datalist ID attribute. First, declare the querySelector() methods. var input = document.
Read more >Autocomplete after serveral chars - Vi and Vim Stack Exchange
I want to use the auto complete feature from vim ( ctrl n ). How can I activate this feature automatically after I...
Read more >RF4 rich:autoComplete with ENTER to start search - JBoss.org
Hi, I would like to change the default behaviour of rich:autoComplete. The default is to wait for N characters and then do the...
Read more >C# tutorial on autocomplete and suggestions - Azure
Learn how to implement autocomplete (typeahead queries and suggested results) when a user starts typing into a search box. In this tutorial ...
Read more >How to work autocomplete textbox on first character search
Textbox autocomplete is not working, exactly for the first character entered first time. After second click, it works perfectly.
Read more >
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The autocomplete is initiated when the third char is typed. This issue is verified on AMO dev with FF59 (Win10).
Here’s the new versus the old behavior
Hey @abiduzz420, it looks like @hellokarthic isn’t working on this bug. Do you want to pick it up?