Bootstrap-select: v2.0.0 Roadmap

[caseyjhol]

• [ ] drop support for IE < 11
• [ ] make 'auto' the default value of dropdownAlignRight
• [ ] remove dropupAuto and replace with dropup where true, false, and 'auto' (default) are options
• [ ] remove support for show-menu-arrow
• [ ] Replace existing title functionality with placeholder. Allow the title attribute to be dynamically generated (like it is currently) or set to static value
• [ ] change default width setting to 'fit' instead of 220px if form-control class not set
• [ ] change default selectedTextFormat setting to 'count'
• [ ] remove data-hidden support for options (can simply use the native hidden instead)
• [ ] replace mobile method with a mobile-optimized version of bootstrap-select, to support all of bootstrap-select's functionality
• [ ] rename old mobile method to something like useNative (open to suggestions)
• [ ] replace actionsBox with something more robust (#1299). Possible usage could be buttons: ['selectAll', 'disableAll']. Allow way to specify location - top or bottom of menu. I'd also like to add the ability to create custom buttons with custom text/function, but I'm still deciding on whether or not to separate this out into another option, such as defineButtons, or have it all under one option.
• [ ] use Bootstrap 4 formatting by default
• [ ] allow liveSearch to be set to an integer (to automatically enable it if above x number of options). default to 10
• [ ] improved templating options (allow option customize the template for everything, including the option to use a function)
• [ ] selectpicker should refresh itself on changes instead of needing to be told (#1360)
• [ ] replace data-style with something more substantial/less confusing. At the very least a rename to data-class might make more sense.

[felixvictor]

Good to see further development.

What about future bootstrap v5 support (ie. jquery removal)? https://github.com/twbs/bootstrap/pull/23586

[caseyjhol]

I definitely want to support Bootstrap 5 and offer a version without jQuery as a dependency. I've already begun removing jQuery code and replacing it with native JS where possible. It'll be much easier to support/maintain once IE < 11 support is dropped, since we won't be as limited and will be able to remove most of the polyfills. I'm thinking that might be a more realistic goal for bootstrap-select v3.0.0, though.

[Amunak]

Can you please try to make V2.0 easier to (re-)style? For starters, allowing us to edit what is now elementTemplates directly through configuration would be great.

I have a fairly specific use case where I not only use a tick icon - I have an "icon" for both "selected" and "empty" state, and they differ from multiselect:

to regular select:

Basically I wanted to make it look like there are checkboxes and radio buttons inside. Currently this is only possible by patching the source, which is less then ideal.

[Organizer21]

One of the reasons I still like Select2 is the option to easy format inputs to show selected rows as tags... is that something possible to add to an improved version of bootstrap select?

[7iomka]

@Amunak - please, please tell me how you implemented what you showed in the screenshots?
I now have almost such a task

[Amunak]

@7iomka sorry, "you don't want to know". I use some ugly patches that directly modify Bootstrap-Select's source when it's pulled by npm install. They break basically every time BS updates.

Because of the issues styling BS and others (like what I reported in #2272) I'm actually considering just abolishing this plugin altogether, either making my own that actually suits me or trying to find out something else :/.

[7iomka]

@7iomka sorry, "you don't want to know". I use some ugly patches that directly modify Bootstrap-Select's source when it's pulled by npm install. They break basically every time BS updates.

Because of the issues styling BS and others (like what I reported in #2272) I'm actually considering just abolishing this plugin altogether, either making my own that actually suits me and doesn't break stuff with every release or trying to find out something else :/.

I'm used another plugin for do that (bootstrap-multiselect)
But after that, I go back justo for experiments and this is result: https://codepen.io/7iomka/pen/xxxZpwN

[kev22257]

Would it be possible instead of allowing liveSearch to be an integer to instead (or additionally) be a function?

"allow liveSearch to be set to an integer (to automatically enable it if above x number of options). default to 10"

[ts1985]

I definitely want to support Bootstrap 5 and offer a version without jQuery as a dependency. I've already begun removing jQuery code and replacing it with native JS where possible. It'll be much easier to support/maintain once IE < 11 support is dropped, since we won't be as limited and will be able to remove most of the polyfills. I'm thinking that might be a more realistic goal for bootstrap-select v3.0.0, though.

Is there any timeline for this? (or first a timeline for v2.0.0?)

[mrlife]

I definitely want to support Bootstrap 5 and offer a version without jQuery as a dependency. I've already begun removing jQuery code and replacing it with native JS where possible. It'll be much easier to support/maintain once IE < 11 support is dropped, since we won't be as limited and will be able to remove most of the polyfills. I'm thinking that might be a more realistic goal for bootstrap-select v3.0.0, though.

Is there any timeline for this? (or first a timeline for v2.0.0?)

@caseyjhol We love this component, because it's the best open source Bootstrap select component available. 🚀

Could you comment a little on the future of this repository/component and whether it is still being maintained? Many thanks!

Here is the Bootstrap release schedule, with Bootstrap 5 scheduled for December 2020. https://github.com/twbs/release#upcoming-release-schedule

[caseyjhol]

I've been absolutely swamped with work as of late, but I'm hoping to get back into continuing maintenance of bootstrap-select very soon. My priorities are:

1. Finalize #899. Or, at the very least get it to the point where that feature is in "beta" and previous functionality is not broken.
2. Add Bootstrap 5 support.
3. Begin immediate work on dropping jQuery requirement.

[teropes]

Feature idea: option to set prefix string or "label" for the select element. It would allow getting rid of external labels that describe what the selection is about. It would be used on both in case of non selected and also when there are values selected.

For example instead of having:
Status: [ None selected ]
Status: [ Queued, Running ]
Status: [ 3 of 6 selected ]

I would like to have string prefix in the input itself:
[ Status: none selected ]
[ Status: Queued, Running ]
[ Status: 3 of 6 selected ]

My value for the option in this case would be "Status: ".

Reasoning for me is that when having inline filter options for some list of data, it takes extra space. In case of typical Search input text box, I might not want to use separate label like Search: [ ], instead I use the input placeholder option and have just [ Search ] so it would be similar UX in these select boxes.

[caseyjhol]

With v1.14.0-beta released, I think I might start work on supporting Bootstrap 5 prior to dropping jQuery as that will most likely require more of an overhaul. While not ideal, you could still run jQuery along with Bootstrap 5 in the meantime.

[zorn-v]

While not ideal, you could still run jQuery along with Bootstrap 5 in the meantime.

No, in bootstrap 5 data attributes was changed with prefix bs-, eg data-bs-toggle="dropdown"

[samihoda]

Any news? I was really hoping for BS5 support.

[bjsintay]

We still use jQuery and BS5. Would be happy with an interim solution that required both.

[caseyjhol]

Bootstrap 5 support has been added in v1.14.0-beta2! jQuery is still required.

[zorn-v]

Is help needed to drop jquery ?