NO BUG: Body font-family set in Theme Styles > Typography is overridden by Bricks default CSS

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL:
Video:

When setting a custom font family (e.g., Rubik) for the Body in Theme Styles > Typography, the setting is not applied on the front-end. The font is correctly loaded—the font files (Rubik-Regular.woff2, Rubik-Medium.woff2, Rubik-SemiBold.woff2) are confirmed loading locally with status 200 in DevTools Network tab. However, but the font-family declaration in the Theme Styles is being overridden by Bricks’ own default stylesheet (10.css), which sets font-family: Arial, sans-serif on the body element.

Steps to reproduce:

  1. Open Style Manager > Theme Styles > Typography

  2. Set Body font family to a Google Font (e.g., Rubik)

  3. Save and check front-end

  4. In DevTools, font-family: Rubik is crossed out, overridden by font-family: Arial, sans-serif from 10.css

Expected behavior: Theme Styles Typography settings should take priority over Bricks default styles.

Workaround: Adding font-family: "Rubik", sans-serif !important in Theme Styles > Stylesheet fixes the issue.

Hi,
Thanks so much for your report!

Unfortunately, I cannot reproduce the problem. Please provide a live link, or send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.

Best regards,
timmse

Hi @timmse ,

I am currently working in a local environment, so I cannot send you the link. I am just wondering if working in the local environment affects this function? I will circle back to this if I still have the issue on the live site.

Thanks!

Ko

No, not really… Please see if you can reproduce the problem on try.bricksbuilder.io :v:

PS: Maybe it’s similar to this one?

Thank you @timmse , The URLs seem to be correct in my case, but after trying Regenerate Code Signature, saving Permalinks a few times, and restarting the Local (dev app), it started to work. I don’t know what exactly fixed the issue. It could be similar to the reference you sent me. Either way, glad it’s working now. Thanks again!

Okay, cool! Let me know if in case it happens again. :v: