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
Hello Dima! I'm developing a filter, and I chose yours as a library for rendering a beautiful selection. You probably designed it for the filter, which is very convenient! But there was a problem with selecting two values in the selector, I set the EventListener to change, and only the first selected value is displayed in the selector, although the native selector has the multiple attribute.
The text was updated successfully, but these errors were encountered:
If I understand the essence of the question correctly, unfortunately, this is standard behavior even in a native select. First and foremost, I strongly recommend passing form data using new FormData, but if it happens that you have to extract and handle them manually, then I added the method getSelectedValues in latest release for you, which returns an array of the values of the selected options.
@afonja14755 Yeah, I was just answering the question, is this getSelectedValues something that shouldn't affect the behavior of the native select.
The way I did it is because I'm using a vue component, so the model does indeed return something an API could accept.
But is nice to have something the library can handle itself, thanks
Hello Dima! I'm developing a filter, and I chose yours as a library for rendering a beautiful selection. You probably designed it for the filter, which is very convenient! But there was a problem with selecting two values in the selector, I set the EventListener to change, and only the first selected value is displayed in the selector, although the native selector has the multiple attribute.
The text was updated successfully, but these errors were encountered: