Mark Lavin

Is this behavior in your own form/front-end or in the admin (or both)?

If I had to venture a guess it's this conditional in the `decompress` which is seeing the `0` and not populating the value: https://github.com/mlavin/django-selectable/blob/master/selectable/forms/widgets.py#L70

The admin as of 1.6 ships with a recent jQuery version so this would potentially only require bundling part of jQuery UI.

Yes the hidden input is cleared with the autocomplete plugin detects a change or select even which likely requires the input losing focus.

selectable does not directly bind to the input change/select/input. It catches the events propagated from the underlying widget from jQuery UI.

Thank you for the suggestion. I'm not sure that section of the docs has been touched in 5+ years. The things I didn't like about `django-ajax-selects` were things that were...

While there isn't an option in the JS plugin that you could pass from the widget, it is currently possible to limit the number of items added on the client-side...

There is an existing jQuery UI demo for this http://jqueryui.com/autocomplete/#categories and I could see this being a welcome addition. --- Original Comment By: [Mark Lavin](http://bitbucket.org/mlavin)

Looks like this breaks Python 2 ¯\_(ツ)_/¯

I've noticed similar issues with the test suite run times when using `hug.test.call` and the similar method based calls. Using `falcon==3.0.0a3` dramatically improves that run time (12+ mins to ~100s)....