Title: Incompatible with CSS Variables
Last modified: November 24, 2019

---

# Incompatible with CSS Variables

 *  [mhogas](https://wordpress.org/support/users/mhogas/)
 * (@mhogas)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/incompatible-with-css-variables/)
 * Hey guys,
 * It seems that Breeze is incompatible with CSS properties coming from `:root {..}`.
 * Unfortunately i can’t share the URL however it could be tested with a stylesheet
   containing something like:
 *     ```
       :root {
         --var1: 14px;
         --var2: #000;
       }
       ```
   
 * .. and then in Chrome Dev. Tools > Elements tab click on the `<html..` tag, and
   these variables shouldn’t be shown, only when Breeze is disabled/or CSS minification
   is disabled. I’m guessing the minification library you’re using is probably outdated.
 * Thanks!

Viewing 1 replies (of 1 total)

 *  Plugin Author [adeelkhan](https://wordpress.org/support/users/adeelkhan/)
 * (@adeelkhan)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/incompatible-with-css-variables/#post-12171282)
 * Hi
 * Breeze supports
    :root { –var1: 14px; –var2: #000; } To view this, you can either
   check the cached version of the CSS file.

Viewing 1 replies (of 1 total)

The topic ‘Incompatible with CSS Variables’ is closed to new replies.

 * ![](https://ps.w.org/breeze/assets/icon-256x256.gif?rev=3352595)
 * [Breeze Cache](https://wordpress.org/plugins/breeze/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/breeze/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/breeze/)
 * [Active Topics](https://wordpress.org/support/plugin/breeze/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/breeze/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/breeze/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [adeelkhan](https://wordpress.org/support/users/adeelkhan/)
 * Last activity: [6 years, 6 months ago](https://wordpress.org/support/topic/incompatible-with-css-variables/#post-12171282)
 * Status: not resolved