-
-
Notifications
You must be signed in to change notification settings - Fork 78.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
Styling input controls globally interferes with other plug-ins - more granular selectors needed #4008
Comments
We'll be sticking with our current selectors. Third party plugin support is never guaranteed. |
The great thing about Bootstrap is you can edit the .css once you've downloaded it! Amazing, right?! |
I don't understand why |
@kcivey Because we'd still need to include |
Great point kcivey! Although if the BS team cannot see the benefits then it's a moot point. So basically anyone using BS will have to override styling 100% of the time on all input controls on all their web pages for all the plug-ins they use that render their own styling for input controls. This seems to chisel away any reason for using Bootstrap. Overriding Bootstrap css in this case seems illogical at best as it implies the BS styling is not correct or as granular as it is supposed to be. It also suggests you realize there is an issue here. Any person who has written a fair amount of css will realize that it is a mammoth task to to take an existing app, converting it to BS and then having to find all non-BS input controls and styling them all. The worst part is that there is no generic styling for this as each input control has a different source/context, some are regular tags and some belong to plug-ins, each with their own flavor of styling. For new web apps the challenge is not that different, each time you add a new plug-in you will have to test all facets of it, and I mean all of it, pop-ups, etc, that contain any kind of input control to make sure it is styled correctly. I am having a hard time seeing the benefits of BS in this context. In order to try and move us closer to a point where we agree on a design that me make a recommendation. If we add a higher-level qualifier to the input selector we may not break anything if we make it "control" and/or "control-group" as they have to be declared inside those classes anyway as far as I understand the design approach of BS. So in my example below can modify the css without possible breaking anything, see the css at the bottom. I tested this briefly and seems to render just as expected. May not be complete as I only spent a few minutes on the css. Your feedback will be greatly appreciated and hopw we can move forward with this.
First Name
Here is the css updates, just pasted the css that needs to be altered:
}
}
} |
Wanted to use bootstrap for the fluid layout (looks great) and some of the beautiful widgets. But uups, I would have to overhaul my project completely because of all the css conflicts with jquery ui and my own css. Deinstalling was a quick decision... |
"BS Team" is fairly descriptive for those who think this is a good approach.... rhollhumer should be appointed as project lead, at least he is sane. |
@barbalex you might want to check out http://addyosmani.github.com/jquery-ui-bootstrap/ if you're looking to use jquery ui |
Thanks! Unfortunately they are not 100% compatible so plug-ins like jqGrid are are fully integrated into jquery-ui have some issues. Having said that, I do use jquery-ui-bootstrap and had to make some minor tweaks to take of edge cases. Date: Thu, 25 Oct 2012 01:09:51 -0700 @barbalex you might want to check out http://addyosmani.github.com/jquery-ui-bootstrap/ if you're looking to use jquery ui
|
@Yohn: Thanks, that's a great help! Am Donnerstag, 25. Oktober 2012 schrieb Yohn :
Alexander Gabriel |
The issue is bootstrap styles input controls globally. For example:
textarea, input[type="text"], input[type="password"], input[type="datetime"], input[type="datetime-local"], input[type="date"], input[type="month"], input[type="time"], input[type="week"], input[type="number"], input[type="email"], input[type="url"], input[type="search"], input[type="tel"], input[type="color"], .uneditable-input {
-moz-transition: border 0.2s linear 0s, box-shadow 0.2s linear 0s;
background-color: #FFFFFF;
border: 1px solid #CCCCCC;
border-radius: 3px 3px 3px 3px;
box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075) inset;
}
This is only one example. When you have plugins like jqGrid for example it interferes with its controls. Bootstrap needs to be more granular in styling controls intended for bootstrap DOM elements and create higher-level selectors. I suggest for the example above to wrap it inside "controls".
Here is another example of styling that interferes with non-bootstrap controls:
select, textarea, input[type="text"], input[type="password"], input[type="datetime"], input[type="datetime-local"], input[type="date"], input[type="month"], input[type="time"], input[type="week"], input[type="number"], input[type="email"], input[type="url"], input[type="search"], input[type="tel"], input[type="color"], .uneditable-input {
color: #555555;
display: inline-block;
font-size: 13px;
height: 18px;
line-height: 18px;
margin-bottom: 9px;
padding: 4px;
}
The text was updated successfully, but these errors were encountered: