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
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
May I suggest a configuration alteration to the angular-ui typeahead plugin to allow for arbitrary input by the user to be bound to the model property if a selection is not made from the drop down.
I come from a Java Swing and Ext JS background where both the Java Swing and Ext JS combo boxes can be configured to either allow random input or not through the 'editable' property. There are legitimate cases for both types and I have used both many times.
I am new to Angular JS and my initial impression from the angular-ui docs is that the Select2 component should be used for non-editable combos and that the typeahead could be used for selections and also accept random input.
Many thanks for considering this,
R.
The text was updated successfully, but these errors were encountered:
Hi,
This ticket comes in response to a suggestion by pkozlowski.opensource from a Stackoverflow discussion:
http://stackoverflow.com/questions/15596765/does-the-angularui-typeahead-plugin-allow-any-typed-value
May I suggest a configuration alteration to the angular-ui typeahead plugin to allow for arbitrary input by the user to be bound to the model property if a selection is not made from the drop down.
I come from a Java Swing and Ext JS background where both the Java Swing and Ext JS combo boxes can be configured to either allow random input or not through the 'editable' property. There are legitimate cases for both types and I have used both many times.
I am new to Angular JS and my initial impression from the angular-ui docs is that the Select2 component should be used for non-editable combos and that the typeahead could be used for selections and also accept random input.
Many thanks for considering this,
R.
The text was updated successfully, but these errors were encountered: