Followup to #11990 #12159
Comments
|
Just set |
|
I already gave a workaround that fixes the problem in my original post; that's not really the point of all of this. I thought that maybe someone would be interested in addressing the issue in a way that makes it works correctly out of the box... |
mdo
added a commit
that referenced
this issue
Jan 10, 2014
Closed
kevinawoo
added a commit
to Loopfirst/bootstrap
that referenced
this issue
Mar 28, 2014
* remotes/upstream/master: (76 commits) grunt dist Update docs per `.container-fluid` addition - Remove `.container-fluid` from "removed classes". - Container isn't fluid by default (`.container`) and `.row` isn't percentage-based, so update docs. Don't test Linux browsers since we don't support them officially and they're failing our tests Fixes twbs#12171: Ensure panel groups have a bottom margin since we nuke it on child panels refer to correct component docs mention for twbs#12188 use height adjectives for greater clarity document twbs#11675 rm outdated `<select>` references from comments in forms.less Clarify that the focus docs styles are not in the repo, per twbs/bootstrap-sass#497 Fixes twbs#11990 and twbs#12159: Make range inputs block level and 100% wide by default grunt dist mixins.less: fix typo in comment use periods for consistency in each line Use absolute instead of relative URLs grunt dist Update paths in bower.json Add new varaible @icon-font-svg-id and set it to be the correct SVG font ID, used new variable in glyphicons.less missing a period after "Twitter, Inc" bump grunt-contrib-jade to v0.9.1 ... Conflicts: Gruntfile.js dist/css/bootstrap-theme.css dist/css/bootstrap-theme.css.map dist/css/bootstrap-theme.min.css dist/css/bootstrap.css dist/css/bootstrap.css.map dist/css/bootstrap.min.css dist/js/bootstrap.js dist/js/bootstrap.min.js less/variables.less test-infra/sauce_browsers.yml
stempler
pushed a commit
to stempler/bootstrap
that referenced
this issue
Apr 11, 2014
… and 100% wide by default
stempler
pushed a commit
to stempler/bootstrap
that referenced
this issue
Nov 4, 2014
… and 100% wide by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@mdo:
Apologies for not commenting sooner, but I have been off the grid in Colombia for the past two weeks.
The JSbin screenshot you posted in #11990 shows exactly the problem that I'm talking about: Despite being contained in a column, the widths of the two controls are not related. That is, the width of the slider is not constrained to the column width in the way that the width of the text box is. This becomes apparent when you resize the browser window: the text box resizes itself appropriately; the range slider does not.
The text was updated successfully, but these errors were encountered: