-
-
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
Text input width #109
Comments
I've seen this kind of thing in other frontend libraries, but I'm unsure about adding them here. The two things I worry about with this are creating class overload and adding design patterns that more easily lead to less compelling visual design. I can see modifying the widths so that they match to a majority of the column widths, but not all. For instance, in what situation does a 760px, 820px-, 880px-, or 940px-wide input make sense? I'm hard pressed to find a situation where that reads or looks well. What sizes are you looking for in particular? I think maxing out at .span8 would be most ideal. Thouhts? |
I tend to agree, on span1-12+ but 100% width 50% and 25% might be of use, Although I tend to put a width on the input and let the containing DIV set the restriction. There always seems to be some issues with how browsers interpret with width (padding, boarders, and input type) I can live without it but would like percentages :) I am building a CMS at the moment and tried the Bootsrap in replace of my own and very little broke (I think that's a good thing) but my CMS is also fluid so my nicely formatted inputs are now kaput. |
Added this to 1.3-wip. Check it out to see it in action. |
Allow the span class to work with text inputs, this would also be useful in fluid layouts.
The text was updated successfully, but these errors were encountered: