css calc height fallback for older browsers

[Ghostavio]

Hello, so I'm using the following in my code:

height: 100%;
height: calc(100% - 55px);

So for browsers without calc support, the first value should be taken, but cssmin is removing it and keeping just height: calc(100% - 55px);, there's anyway to keep this particular duplicated css attribute without disabling all the duplication removal, or maybe creating a rule for this specific case?
In case it's not possible, how would I completely disable the check for duplication?

Thanks.

[jakubpawlowicz]

Could you share your cssmin setup? I can clearly see it works fine in any 3.x:

> echo "a{height:100%;height:calc(100% - 55px)}" | ./bin/cleancss
a{height:100%;height:calc(100% - 55px)}

[jakubpawlowicz]

I'll close it for now, but please reopen if needed.

[ahmedelgabri]

@jakubpawlowicz I have the same exact issue and here is how you can reproduce the problem.

This looks fine

 $ echo ".foo { display: block; display: flex; color: green; align-items: center; }" | ./node_modules/.bin/cleancss
.foo{display:block;display:flex;color:green;align-items:center}

This is not, I moved color between the two display declarations

$ echo ".foo { display: block; color: green; display: flex; align-items: center; }" | ./node_modules/.bin/cleancss
.foo{color:green;display:flex;align-items:center}

It's very subtle but developers will expect their code to work the same in both situations. For now advanced: false fixes this but I think that this behaviour should be normalized. Not sure how since it's a very hard problem to determine when it's a fallback and when it's a duplicated declaration.

[jakubpawlowicz]

@ahmedelgabri you can also use aggressiveMerging: false for the same effect. Solving this is dependent on #290.

[ahmedelgabri]

Thanks @jakubpawlowicz