shorthandCompacting: background not merging properly with -[webkit|moz|o]-linear-gradient

[collinsethans]

I have the below css for transparent facebook logo on a gradient:

.facebook-login {
    background: url(http://www.example.com/fb-logo.png) no-repeat center, -webkit-linear-gradient(top, color1, color2);
    background: url(http://www.example.com/fb-logo.png) no-repeat center, -moz-linear-gradient(top, color1, color2);
    background: url(http://www.example.com/fb-logo.png) no-repeat center, -o-linear-gradient(top, color1, color2);
    background: url(http://www.example.com/fb-logo.png) no-repeat center, linear-gradient(top, color1, color2);
}

Using shorthandCompacting, the above is reduced to:

.facebook-login {background: url(http://www.example.com/fb-logo.png) no-repeat center, linear-gradient(top, color1, color2);}

Due to this, the fb logo is not shown on several browsers.

I have current work-around by setting shorthandCompacting: false.

[jakubpawlowicz]

@collinsethans Thanks for raising this issue. I'm currently at the point of rewriting compacting code so will definitely look at it soon.

[collinsethans]

@jakubpawlowicz Thanks for acknowledging, it will be great to have these fixed. I am currently using this on production, will you have a ballpark timeline by when you may have the new code released?

Another feature that I was thinking will help much here is if there's some log on what gets compacted and/or optimized to what. That will give us a lot of confidence when using in production. (The above bug went unnoticed and was pointed by an user after a week of release). Will you have any plans on adding such logging feature?

[jakubpawlowicz]

I plan to release 3.2 in 1-2 weeks from now, as I'm nearing completion of internals rewrite.

Interesting idea about the log. It could be rather verbose unless we'd narrow it to something like shorthand compacting only.

[collinsethans]

@jakubpawlowicz Hi, thanks for the timeline.

Yes, the logs will be very verbose, but then it's easier to validate the output and issue identification is quick, thus builds confidence. And, it will run only with a switch, non-default. To begin with, it can be for anything and everything that the tool is going to optimize in the file.

[jakubpawlowicz]

@collinsethans let's see what can be done here. It would need to provide a list of optimizations made to properties and selectors, which won't be straightforward to add. I've opened #514 to cover it.

[jakubpawlowicz]

Fixed in master with #490.