Precedence of JavaScript variables about postcss-custom-properties HOT 9 CLOSED

Why not.
But what about handling !important when parsing custom prop ? I'm not sure we are currently supporting it.

from postcss-custom-properties.

How is !important parsing related?

from postcss-custom-properties.

It was just an idea to make user able to get javascript defined as a fallback OR more important.

variables: {
 "--test-one": "js-one !important",
 "--test-two": "js-two !important",
 "--test-three": "js-three"
 }

:root {
 --test-one: local;
 --test-two: local !important;
}

div {
 color: var(--test-one);
 color: var(--test-two);
 color: var(--test-three);
}

Could give

div {
 color: js-one;
 color: local;
 color: js-three;
}

Take a look to this example using firefox http://jsbin.com/qefano/1/edit You should inderstand what I mean.

from postcss-custom-properties.

This one is even better http://jsbin.com/qefano/2/edit

from postcss-custom-properties.

If that is spec-ed behaviour, then we should definitely add support for it to the lib. But I think JS-defined is a different issue and should act as if you're appending :root declarations to the end of the CSS document. That way you could also override CSS-defined !important values :)

from postcss-custom-properties.

FYI I've opened a new issue for the !important thing #12

from postcss-custom-properties.

Would it be ok to be collab on these repos you ported? I'm moving our stuff over to postcss.

from postcss-custom-properties.

Added as owner for postcss ;)

from postcss-custom-properties.

Thanks Maxime :)

from postcss-custom-properties.