You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We strive for the most complete transformation but we/no plugin can achieve true complete parity according to the [specification](http://dev.w3.org/csswg/css-variables/) because of the DOM cascade unknowns.
`post-css-variables` plays really nice with [`postcss-nested`](https://github.com/postcss/postcss-nested) in order to get a larger subset of CSS variables features. *See [Nested rules, Usage section](#nested-rules)*
220
+
`postcss-css-variables` plays really nice with [`postcss-nested`](https://github.com/postcss/postcss-nested) in order to get a larger subset of CSS variables features. *See [Nested rules, Usage section](#nested-rules)*
221
221
222
222
If you are using [`postcss-custom-properties`](https://github.com/postcss/postcss-custom-properties) previously, we have a compatible feature set and more so you can switch over without having to refactor any of your code. You can just start writing the new awesome stuff.
223
223
@@ -230,7 +230,7 @@ There is another similar plugin available, [`postcss-custom-properties`](https:/
230
230
231
231
### Differences from `postcss-custom-properties`
232
232
233
-
The main features that we`post-css-variables` add/provide are:
233
+
The main features that we`postcss-css-variables` add/provide are:
234
234
235
235
- No limitation on what scope CSS variables can be declared or used (`:root` or wherever)
236
236
- Proper value substitution based on explicit DOM/structure traversal
0 commit comments