-
And how explicit should that access be?
- The initial proposal suggested explicitly passing in any variables needed, as part of the parameter list
- The more recent proposal involves a `using ()` …
-
Currently, the custom properties available to developers for each message are only available when the DOM is inspected. it would be great to have some documentation surrounding these properties.
-
The scope of this "RFC" is to discuss about the possibility to use CSS Custom Properties for dynamic styles.
Switching to use CSS Custom Properties might allow us to explore static extraction in t…
-
There is a small room for improvement after #111 has been merged: as of now, custom CSS properties are in the reverse order (compared to how they are annotated in JSDOc).
I would recommend to eithe…
-
The `CSS.supports()` method allows a two-parameter `property, value` syntax. [According to the spec](https://drafts.csswg.org/css-conditional-3/#the-css-namespace), the property can be a CSS custom pr…
-
Hey, is it possible to reference the values variables in the custom CSS properties?
```
@value mycolor: #fff;
:root {
--first-color: mycolor;
}
```
I see `mycolor` persisted as it is, I…
-
### Issue type
**I'm submitting a ...** (check one with "x")
* [X ] bug report
* [ ] feature request
### Issue description
**Current behavior:**
after register a custom css property…
-
Input:
```twig
{% htmlcompress %}
.foo {
--a: 1em;
padding: var(--a);
color: blue;
}
{% endhtmlcompress %}
```
Expected output:
```html
.foo {--a: 1em;padding: var(--…
Grawl updated
4 years ago
-
Should the following test-case be brown or yellow?
```html
a {
--foo: brown;
}
:visited {
--foo: yellow;
color: var(--foo);
}
Which color?
```
Right now Geck…
-
Hi,
the following code fails to be expanded:
``` css
:root {
--my-color: red;
}
.test {
border: 1px solid var(--my-color);
}
```
and raises the error:
`postcss-shorthand-expand failed to …