New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autocomplete: autoFill option implemented #7
Conversation
…oses completion if there is exactly one suggestion
We don't want this in the core of the plugin. |
And I don't see any nice way to do this from user side. Also, why? Give me just one reason. |
Because it's not necessary and adds some complexity. If we implement everything anybody wants, we end up with 30 options that way. Also, this is very easy to do from the user side. Listen for the open event and check the number of items. |
...you should look at how many hacks are listed on StackOverflow since this option was removed... |
This option wasn't removed; it never existed in the first place. |
No, it's a new plugin from scratch. We used that autocomplete only as a reference to functionality that should be easy to accomplish.
No matter how many links you point to, I assure you this is a nice to have. We would have several tickets filed for this and everyone would be clamoring for this to be added. This is definitely not the case.
And you'll get similar results for many other features as well, should we just triple the size of the API? Please read http://blog.jqueryui.com/2011/03/api-redesigns-the-past-present-and-future/
Feel free to file an issue and clearly explain how this is bad usability. You'll need some really convincing data. |
Ok, I see you're working to simplify the API. Didn't knew that. Thanks for the quick reply. |
Simple change, will not affect existing code by any means. Nice-to-have feature.