Allow to enforce applying optimisations to custom property values about csso HOT 8 OPEN

@ygoe Could you please provide an example? The single case I can imaging is a value of custom property.

from csso.

Indeed, I observed this with a custom property:

.something
{
  --link-hover-color-l: calc(var(--link-color-l)
  	+ max(0%, (100% - var(--link-color-l)) * var(--link-hover-lf))
  	- max(0%, var(--link-color-l) * (0 - (var(--link-hover-lf)))));
}

from csso.

Custom properties can contain any content, that's not a regular value but a part of it when substituted. Removing anything from a custom property may break something. So CSSO do nothing with such values for now. Probably we need to add an option to enforce optimisation for such value in case you are sure it doesn't break anything in your case.

from csso.

Custom properties currently get trimmed, which creates a different output for development/production modes:

.c {
  --x: aaa bbb ; 
  --y: zzz ; 
}
/* OUTPUT: removed whitespace before and after the custom properties values */
.c{--x:aaa bbb;--y:zzz}

Edit:
Although this is the opposite of what the author is requesting, I think that the default behavior should preserve the value as is, untrimmed, and an option could be added to select between preserve/trim/min-whitespace

from csso.

What's the difference of these additional spaces? I'm not aware of any situation where it's relevant.

from csso.

getComputedStyle(node).getPropertyValue('--x') returns the untrimmed value

from csso.

I still don't need those extra spaces and cannot imagine a scenario where I would ever need it. CSS usually doesn't preserve such spaces and any application that now does is highly unexpected and probably bad design.

from csso.

I take it back, looking at the csswg it seems that custom properties should be trimmed. Browser implementation currently fail in my case.

from csso.