You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observed behaviour: When we renderInputComponent with out own styled input, we loose the on change triggered by the up/down arrow and enter keys. What do we need to include into our custom input to still trigger those?
Expected behaviour: arrow key highlighting works with rendered text inputs
Are you making a feature request?
Please describe your use case from user journey point of view, e.g.:
In my application, when developer is using a custom input component via renderInputComponent will still trigger onchange via up/down and tab/enter keys
If you have ideas how to extend the Autosuggest API to support your new feature, please share!
If you know any examples online that already implement such functionality, please share a link.
The text was updated successfully, but these errors were encountered:
Are you reporting a bug?
Observed behaviour: When we renderInputComponent with out own styled input, we loose the on change triggered by the up/down arrow and enter keys. What do we need to include into our custom input to still trigger those?
Expected behaviour: arrow key highlighting works with rendered text inputs
Are you making a feature request?
Please describe your use case from user journey point of view, e.g.:
If you have ideas how to extend the Autosuggest API to support your new feature, please share!
If you know any examples online that already implement such functionality, please share a link.
The text was updated successfully, but these errors were encountered: