-
Notifications
You must be signed in to change notification settings - Fork 23
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
Deselection with single-select abp-select #60
Comments
Ok but even when using |
not sure to understand, can you provide some examples of what you mean in code |
What I meant is: When the end user decides that he wants to deselect the current selection, he needs some UI element (the trigger element I was referring to) to click on. This element can then call Moreover, I just discovered that |
Hm so I think the issue is rather with the wrapped bootstrap-select that is used by abp-select. See snapappointments/bootstrap-select#1449 for similar requirement as mine that is not yet supported by bootstrap-select. The suggested workaround uses the |
It's possible since I had to write/expose them all 1 by 1, so I could have missed some and/or if something is not well documented then it won't show up in |
I will test if the workaround with |
The workaround with <abp-select picker-options.bind="{maxOptions: 1}" multiple></abp-select> |
Provide an option to add a deselect option to the options list of an abp-select. When the user selects this option, the backing value binding should be set to
null
or to some user-provided value.@ghiscoding I'm not sure if this should be handled by the component or if it is better to leave this to the user. What do you think?
The text was updated successfully, but these errors were encountered: