Bricks Version: 1.5 RC
Browser: Any (tested on safari)
OS: macOS / Windows / Linux / etc.
URL: dev.ultimatetradingjournal.com/uk
Setting fonts in theme style do not work after publishing. After investigating in the dev tools it is clear that the builder sets double quotes on the font family and it does not get recognized by the browser. see screenshot below:
Hello @zemdei,
Thank you for your post.
I’m not able to reproduce this issue on my side. Did you import or migrate this template/page from anywhere?
Is it possible to grant us access to your WordPress dashboard so we could check?
Thank you!
Luis
I’m getting the same thing in the stable version. I have uploaded Plus Jakarta Sans as a custom font and set it in the theme as the body text. All browsers are not displaying it because they are marking it as an invalid property. Is it that Bricks is enclosing any custom font name that has spaces in quotes which are then being passed to the browser which also encloses in quotes?
The problem happens because the body font set in theme is not being ‘displayed’ in the Style > Typography’ tab of the basic text element. I had to go into the theme, change the body font from the custom one to a standard font (arial), save and then change it back to the custom font and save. The custom font name was then displayed in the Style section (greyed out). The page then viewed correctly on the front end with the font correctly shown in the inspector without double quotes. Is there a bug in that for custom fonts, Bricks isn’t carrying it through to the Style > Typography tab initially?
Hey Guys,
We were able to reproduce the issue in the meantime: WIP: Various element typography styles reverts to default styling when breakpoints are selected
Best regards,
timmse
Brilliant, thanks Stefan.
Thanks for the update - any news about a possible hotfix?
As far as I can see, the problem only occurs with custom fonts. That means the only temporary solution is to do without custom fonts. I know… not satisfactory 
However, it won’t take that long until 1.5.1…
I think not just custom fonts. The problem is font name having more than one word separated by “space”. So there would be quotes added to them. One word font name or words separated by dash would not have this bug. You can try with any google font coming with the builder that has two or three words name.
Hi @zemdei @simon @mdomedia @frozenwind,
We’ve fixed this bug in Bricks 1.5.1 RC, which is now available as a manual download in your account.
Please let us know if you are still experiencing issues.
Best regards,
timmse
