-
Notifications
You must be signed in to change notification settings - Fork 486
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
How to override the Bootstrap navbar-default-bg variable? #146
Comments
I'm also having this issue. Have you found a work around yet? |
@danecjensen At the time, no, I wasn't able to find a way around it, so I reverted to 2.3. I don't know what's up with it. Strange that it's still broken. |
Try this:
It works for me. Note that the rails_layout gem sets up a navigation partial that uses the Here's a list of all the Bootstrap variables. It's not easy to figure out how each is used. |
As noted above, I can override the In principle, if I remove the
But it doesn't work. So I'm wondering why it is possible to override some variables and not others. This is not really the right place to report the issue, as I don't believe it has anything to do with Rails Composer. I have opened an issue for the rails-bootstrap example app. Maybe it's best to open an issue on bootstrap-sass. |
I'm closing the issue here since it's now an open issue elsewhere: RailsApps/rails-bootstrap#12 |
hi , the variable are getting from bootstrap/variables and setting up the vavbar color in bootstrap/navbar , this applying the color in navbar with the variable navbar-default-bg . look into the code below if you want to change the color you have to do the following. // Core variables and mixins this will work fine , analyze the execution cycle. but i am suggesting use the other class for applying the bg-color instead of over riding. |
Discussion of the open issue is here: |
When building a custom app with Rails Composer, and selecting Bootstrap 3 (which presently installs 3.0.3.0), overrides are not working straight out of the box the way it does with version 2 (substituting the new variable names), though https://github.com/thomas-mcdonald/bootstrap-sass says it should retain the same behavior. E.g., putting the Bootstrap $variables ahead of the framework @import.
I did not see any issues related to this under the specific gem (bootstrap-sass); so I'm wondering if it's a composer configuration issue.
The text was updated successfully, but these errors were encountered: