Button drop down documentation seems to be missing

[TheWilks]

Have you stopped supporting button drop downs? I can not seem to see the documentation.

http://wet-boew.github.io/wet-boew-styleguide/v4/design/buttons-en.html#btn-dropdowns

[pjackson28]

@wilkmit They were never supported as WET does not include any Bootstrap JS. Documentation about them was inadvertently left in for a period of time after copying and pasting over some of Bootstrap's documentation (but the examples never worked since the JS was never included).

[TheWilks]

Thanks for the quick response. Nothing similar was included in WET 4.0 I assume?

[pjackson28]

Not the pull-down button exactly as usability issues were flagged with such an approach. What are the use cases you are trying to cover with a pull-down button?

@thomasgohard What to do you recommend instead of the pull-down button? Are there good alternatives in WET or are there good options that can be added (considering the usability concerns raised in the past)?

[TheWilks]

I ended up using the light box with the select drop down. Ideally I wanted to style the options in the drop down but I can live without it.

[CalvinRodo]

We have a use case where we would like to use drop down buttons in a list of items that have different types of actions that can be performed on each of them

Here is an mockup that we were hoping to use.
http://www.bootply.com/Y35iKIMjOH

Now I can easily replicate the drop down behavior using a small bit of custom javascript since the css classes are still there, but it would be nice to not have to do that.

So is it possible to either add in Javascript for the drop down buttons or remove the Button drop down css from Wet.

Also if this is something that won't be added can you suggest some alternatives?

[hsrudnicki]

@thomasgohard @pjackson28 @wilkmit @CalvinRodo : Are you ready to close this issue?

[CalvinRodo]

@hsrudnicki Unless there has been some consensus to either add back in the drop down or remove all remnants of it from the CSS then no it cannot be closed.

[LaurentGoderre]

We don't touch upstream dependencies and I am not sure we will add any JavaScript for it

[hsrudnicki]

... and further discussion needed, at least please update this issue's status whether this issue can be closed or otherwise? Thank you

[hsrudnicki]

Is this above still an issue, waiting for your consensus to resolve/fix it? Either way, please update this issue's status, whether this issue (in regards to content styling, bootstrap, as well update of Documentation, ...) can be closed as resolved/fixed or if otherwise? Thank you

[hsrudnicki]

Is this still an issue? Can be this closed or otherwise? Please update the status of this in regards to the current year, thank you

[hsrudnicki]

Due to no further discussion/updates, this issue of 2014 year can be closed. If you think otherwise, please again update the status of this, thank you