-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Setting the form-class on b-dropdown-form #4474
Closed
bbugh opened this issue
Dec 9, 2019
· 1 comment
· Fixed by #4475, mariazevedo88/hash-generator-js#24, tghelere/CL#8, tghelere/CL#10 or mariazevedo88/hash-generator-js#26
Closed
Setting the form-class on b-dropdown-form #4474
bbugh opened this issue
Dec 9, 2019
· 1 comment
· Fixed by #4475, mariazevedo88/hash-generator-js#24, tghelere/CL#8, tghelere/CL#10 or mariazevedo88/hash-generator-js#26
Labels
Comments
The current workaround would be a custom style that targets the form element, but with scoped styles you would need the vue-loader deep selector: <style scoped>
.special-form /deep/ form {
flex-wrap: nowrap;
}
</style> But a new prop |
20 tasks
Merged
This was referenced Jan 17, 2020
This was referenced Feb 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe...
We have a
b-dropdown-form
that needs to be aflex-wrap: nowrap
, among other settings. There is currently no way to set the class on the form of theb-form-dropdown
. Usingclass="special-form"
adds the class to the wrapperli
.Describe the solution you'd like
The common pattern in these scenarios seems to be having a new property that affects the specific component, like
form-class
.Happy to PR this if it's an acceptable idea.
Describe alternatives you've considered
We could use a selector to say
.special-form > form
but that's getting into library implementation details.Additional context
https://bootstrap-vue.org/docs/components/dropdown#comp-ref-b-dropdown-form-props
The text was updated successfully, but these errors were encountered: