Add on_blur trigger for Autocomplete component

[BobserLuck]

Is your feature request related to a problem? Please describe.
Not directly. But parity with other text like inputs would be fantastic.

Describe the solution you'd like
An additional on_blur Event trigger for the Autocomplete Component.

Describe alternatives you've considered
Autocomplete does have the raw on_input Event. Though, as mentioned on the Input Component documentation, this can hinder performance if every keystroke is going back to the server.

Additional context
A form allowing an Autocomplete field as both having suggested inputs but also treated as a standard text input. Allowing more efficient server updates if text is entered but not part of any selection. This can be done via on_input, but that sends every keystroke to the server, and other text input Components recommend using on_blur in light of that.

[richard-to]

This a fair point. When I implemented the auto complete originally I had wanted to add on blur, but there was some undesirable behavior in relation to autocomplete drop down selection behavior. I don't fully remember the issue. I'll try to revisit this again and see what the issue was and if there's a potential workaround.

[BobserLuck]

Thanks for being very responsive on feedback for this project. It certainly has proven an awsome framework for Python apps for fast deployment.

For this issue in particular, maybe a shot in the dark, but would it be something to do with what happens when you select an item? It looks like the selection box flickers off focus for a fraction of a second when an item in the list is selected and populates the input field. Would it cuase the two events to trigger simutaneasly?

[richard-to]

Yes, I think that sounds like the issue. The blur event getting triggered when trying to click an item on the drop down. But maybe there's a workaround where we can prevent sending the blur event in certain cases where it would not make sense. Not sure though. I'd have to test it out.