use @grid-float-breakpoint-max

[bassjobsen]

fix for issue #10371 (and #10395)

[bpugh]

Just curious why this wasn't merged... is it not a valid issue?

[cvrebert]

@bpugh It hasn't yet been merged, but it will be (or a substantially similar fix will be applied).

[cvrebert]

Missing a @ for grid-float-breakpoint ?
Also, there should be a space after the comma.

[ShaunDychko]

There isn't a "max" function listed at http://lesscss.org/#reference.

[cvrebert]

They're adding one for v1.5 (https://github.com/less/less.js/blob/v1.5.0-b3/lib/less/functions.js#L311 ), but that's still in beta, and we're still stuck way back on v1.3.3 due to Recess.
So, this ain't gonna fly.

[cvrebert]

maybe call it @width instead of @a ?

[cvrebert]

Also, this is more of a "clamped" than a "max".

[mdo]

This needs updating with master, the new variable added to the customizer, and then documented for it's own use somewhere as well.

Also, your formatting is a little off from the rest of the framework so that opening curly braces are on the same line as the rule and no extra spaces appear between nested parens.

[mdo]

Also bumping to 3.0.2 for now.

[cvrebert]

We should also update the .table-responsive media query; see #11086 (comment)

[bassjobsen]

an other way to calculate max() in Less, see: http://stackoverflow.com/a/19386571/1596547:

.minmax(@a,@b,@unit:'px') {
  @min: ~"`Math.min(@{a},@{b})`@{unit}";
  @max: ~"`Math.max(@{a},@{b})`@{unit}";
}
.test {
  .minmax(700,800);
  width: @max;
}

[jamiebuilds]

@cvrebert I can make the update to .table-responsive, I ran into the issue on my own and have made the change.

Update: check out the diff https://github.com/thejameskyle/bootstrap/compare/patch-1 (the compiled file will have the correct max-width once this PR is merged)

[mdo]

I still don't understand what you're trying to accomplish here. Compiling with grunt on this doesn't work—it errors out on your original assumption of setting the @grid-float-breakpoint var to 0.

Let's start fresh with a new PR and some more explanation around this.