Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

1.3K

As minified, when using these properties on :root:

:root{--body-color:rgb(0, 115, 230);--th-navbar-pure-g:#09f;--secondary-color:#00bfff;--hover-button-color:#00bfff}

and then implementing these CSS properties:

.th-navbar.pure-g{background-color:var(--th-navbar-pure-g)}.th-subbar.pure-u-1{background:var(--secondary-color);border-bottom:1px solid #fff}body{background:var(--body-color)}

I get and .

As minified, when using these properties on :root: `:root{--body-color:rgb(0, 115, 230);--th-navbar-pure-g:#09f;--secondary-color:#00bfff;--hover-button-color:#00bfff}` and then implementing these CSS properties: `.th-navbar.pure-g{background-color:var(--th-navbar-pure-g)}.th-subbar.pure-u-1{background:var(--secondary-color);border-bottom:1px solid #fff}body{background:var(--body-color)}` I get [this](https://pic8.co/sh/31vI3G.png) and [the CSS appears broken](https://pic8.co/sh/ggqyQB.png).

(post is archived)

[–] • 1 pt

Global values are ignored for security reasons.

[–] [deleted] • 0 pt

What I'm trying to do is implement CSS custom properties so as to make it easier for anyone who wants to reuse Bluewave Rouge, the theme for , to also be able to very easily customize it. Here's what CSS custom properties are: https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties

Which brings me to the question, what "security reasons" would give Poal reason to not support CSS custom properties?

[–] • 1 pt

Check out Throat’s code about custom css validation and you’ll understand why.

[–] [deleted] • 1 pt

Ah, so it's related to the Throat source code's custom CSS validation methods as to why it's not supported. Would be able to check it but it looks like https://phab.phuks.co is down due to a MySQL connection issue right now. :/