-
Notifications
You must be signed in to change notification settings - Fork 327
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
New "selectize" script #516
Comments
Ah, and the SCSS of selects doesn't render "optgroup" header, they have the same look of the other options. |
Just discovered Selectize completely removes any data-attributes of the original select options, definitely not a big deal, how can I retrieve original data... may I ask you why have you decided to abandon Chosen? Chosen allowed to work with selects via javascript and only rendered their look, with selectize the original select box seems disappeared and unreachable, I have to manipulate via selectize only. Am I right? |
The problem with select2 was that there were lots of conflicts with other plugins that were also using it (for example ACF), it's more difficult to style than selectize, and also selectize is a lot lighter. |
oh, and also it has the ability for multi-selects as well as reordering the selected items out of the box. ;) |
I see... thank you for your precious time |
Hello, in version 1.0.2 I created my custom fields to manage custom Google and Typekit fonts, and I assigned the class "select2" to enable chosen for those fields (also discussed here #326). Is there a class to enable "selectize" on version 2.0+ or have I to inititialize the script personally on my JS file? I don't want to risk the bad performance like in the issue above.
Thank you.
The text was updated successfully, but these errors were encountered: