Fallbacks added everywhere even on IE >= 10

[randomdevpete]

I am seeing px fallbacks added for every rem rule (not just those in pseudo-selectors or font shorthands) when my browserslist is set to "Explorer >= 10".

I believe the intended behaviour is that this should only happen for IE <= 8 ?

[iamvdo]

We have a test for that and it works as you expect
https://github.com/robwierzbowski/node-pixrem/blob/master/test/test.js#L247-L252

So, your problem might be elsewhere ?

[iamvdo]

Maybe your problem is related to #38 ?

[MoOx]

Maybe meanwhile, cssnext should pass the option (I know @chucksellick use it).

[iamvdo]

@MoOx : It could be great indeed.

[rafaelrinaldi]

@MoOx @iamvdo this is also being an issue for me. I'm currently using pixrem through cssnext and it seems to bypass the rules I specify on the JSON configuration file.

[MoOx]

Ok we added something in cssnext, but it appears to be unnecessary (if I keep the added test, but remove the code changed, pixrem still add rem for IE 9 and IE 10 (eg on body for font-size).
@iamvdo does this plugin add every rem as px for every rules until IE 11 ?

[MoOx]

From what I am seeing here

node-pixrem/test/test.js

Lines 268 to 273 in c21d67a

	it('should add fallback only for font and pseudo-element when IE9 is in scope', function () {
	var css = '.rule{width: 2rem;font: bold 2rem sans-serif}.rule::after{width: 2rem}';
	var expected = '.rule{width: 2rem;font: bold 32px sans-serif;font: bold 2rem sans-serif}.rule::after{width: 32px;width: 2rem}';
	var processed = postcss([pixrem({browsers: 'ie 9'})]).process(css).css;
	assert.equal(processed, expected);
	});

you have specific behavior for IE9.

[MoOx]

Ok my bad. PR was incorrectly refering to pixrem as the name of the feature, but it's "rem" in cssnext. So it's now ok in cssnext :)