Doc bug *or* feature request: Combo breakpoints + fallbacks about susy

[mirisuzanne]

That is exactly how it works, and has been working fine for me. Can you show me what happens when you try it?

BTW - ie fallback class is a simple string, without the "." (I should probably document that, if I didn't).

[alanhogan]

oh… yeah, that was probably my mistake, then — I was passing the class name with the leading dot.

Hmm.

Is there a programmatic way to strip a leading dot in sass?

[mirisuzanne]

Not yet, but it's coming: sass/sass#401

In the meantime, it's easy add the leading dot in Sass:

$ie: lt-ie9;
$ie-class: ".#{$ie}";

There are actually several ways you could write that, I think.

I wonder if there's a way for me to check and accept either one? I imagine that would be coming in the same commit I linked above...

[alanhogan]

Right, yeah.

I ended up just using the IE class as you suggested – the reason this was a (small!) issue at all, and why I asked about removing the leading dot, was that I have a Sass function that takes a browser identifier like “ie” or “ie8” and generates a selector that matches our body tag in that browser or browsers (.brwsr-X); the idea was it could be used throughout the project and if we changed how browser detection happened we’d only have to change this function. (And I did already, going from body.brwsr-X to just .brwsr-X for less specificity.) But since I’m only using susy’s grid mixins directly in a few places, it’s really not a big deal at all

[mirisuzanne]

Documented by: e3ebfbf