-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Dropping support for 'selectize' theme? #175
Comments
Related to #186 |
My thought is as follows: Pleeeeeease never drop selectize support. I think it fits better in Bootstrap (seems irrational, but I mean selectize-default not bootstrap-2 and 3) and looks more clean and coherent as select2. |
Pretty please, my company has 3+ projects using the selectize theme. We think it looks/functions the cleanest. Thanks for your great work, ui-select has been amazing and its crazy how fast you guys have cranked! |
+1, i also used selectize theme, and just like previous comments, selectize theme looks cleaner and fits better in overall.. I also need multiple selection as well, please don't drop selectize theme. thanks. |
I think that maybe the best way to keep support for selectize styles will be to start checking the proposal at #186 |
Awesome, thanks for the update. The packaging seems like it would be very cool. |
No update since last fall, any news on the support of the multi selection for selectize ? |
This seems like something that isn't happening, so closing unless the new maintainers feel it's something they want to consider - if they view it as an issue, it'd be better for a new issue to be open, this issue seems a bit misleading at this point. |
Not sure how many users actually use the selectize theme, but we might get delays on some features if we need to keep 3 themes in sync.
I've no problem keeping bootstrap and select2 themes (since I actually used them on some projects), but for example I see that some code refactoring might be needed to support selectize in PR #138 (to support multiselection) since the css on selectize is very specific on the parent/child.
Anyway let me know your thoughts.
The text was updated successfully, but these errors were encountered: