SOLVED: Various element typography styles reverts to default styling when breakpoints are selected

Bugs
1

Bricks Version: 1.5 stable
Browser: Latest Firefox
OS: Windows 10
URL: See Looms below

When using custom fonts on the heading and nav menu elements via the typography settings of that element, the element loses its font styling in the builder and the front end when switching between breakpoints. Please see the loom video for more details.

Note, this also happens with font styles from the theme style panel as well.

UPDATE: This bug also happens to text on the Menu Nav element:
Video 1 Loom | Free Screen & Video Recording Software | Loom
Video 2 Loom | Free Screen & Video Recording Software | Loom

3 Likes
2

The bug also persists when setting the font at the theme style level. Still reverts at that breakpoint.

1 Like
3

I’m having similar issues with Custom Fonts and typography styling reverting at breakpoints.

1 Like
4

Glad I’m not the only one! A pretty frustrating bug for sure.

5

Hey mdomedia,
Thanks so much for your report!

I was able to reproduce the issue with custom fonts and added it to the bug tracker.
It seems as if there are some doubled quotes messing up the styles.

Best regards,
timmse

2 Likes
6

simillar problem, on the mobile breakpoint bold weight text seems to revert back to normal. changing the font weight or adding the strong html tag tag does not make any changes

1 Like
7

I think not just custom fonts. Even the “Times New Roman” in standard font has this behavior. The 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.

3 Likes
8

This is what happens:

  1. Select the font name more than two words.

    image
    image1402Ă—803 95.8 KB

  2. Change breakpoint. You can see the font name was wrapped by quotes.

    image
    image1215Ă—693 111 KB

  3. Change breakpoint again. The font was lost and switched back to default theme font.

    image
    image1299Ă—735 140 KB

3 Likes
9

Are you using ACSS??

10

Nope just vanilla 1.5

11

The Bug also happens when going to different pseudo actions. like Hover - Active - Focus.

2 Likes
12

Big time issue, and a pain, no idea how to even mitigate it. It just keeps reoccurring

1 Like
13

By far the biggest oversight I’ve seen in a Bricks update so far. Pretty frustrating as this has completely sidelined a project I’m involved in that’s using several custom fonts :upside_down_face:

14

If you are using custom fonts, then as a temporary workaround, merge their name (Lucida Sans = LucidaSans) when the problem is solved, return back :slightly_smiling_face:. Translator.

1 Like
15

Maybe that is affecting the conditions as well! I’m under the impression that there is some code that is not closed properly here and there…good luck bug squashing!

1 Like
16

Just vanilla Bricks 1.5 for me too.

17

Yes, I can confirm its not just custom fonts having the issue. Seems to be an issue with typography in general.

1 Like
18

Is there a solution in sight? As I’ll have to wait to push a site live. Having trouble as well with custom fonts all over de site.

1 Like
19

1.5.1 comes on the weekend or early next week that will bring a fix.

20

Source for this claim of 1.5.1?