NO BUG: Font fall back on typography settings

Bugs
1

I’m not sure if this is a bug or if it is the intended behavior.

In the builder, if we go to:
- Settings > Theme Styles > Typography
We have the option to choose a fallback font.

chrome_zPuTQfhTAC
chrome_zPuTQfhTAC510×518 16.4 KB

But, if we are building a page, we don’t have that option in the typography settings of that element

chrome_mw9N73nvsu
chrome_mw9N73nvsu517×667 18.5 KB

This might not be important, but I had a use case for this when the only solution to have the ‘All rights reserved’ symbol (®) next to the title of a product was to use ‘monospace’ as the fallback.

In this case, I couldn’t use any solutions like wrapping the symbol in a span or sup tags.
This particular custom font ‘Metropolis’, the file I got didn’t had that glyph as it seems. So the quick solutions was to add ‘monospace’ as a fallback.

I needed to have the ® without serifs and on top of the name.
Example without setting monospace as fallback:
chrome_fMKu9ehNRc

Example with monospace as fallback:
chrome_BpR3y19U9P

2

Hi Marcio,
Thanks so much for your report!

The fallback font settings were and are only available in the theme styles and not in the individual font settings. Accordingly, this is not a bug, but possibly a feature request. As far as I know, you’re the first user with this request.

However, it is relatively simple to deal with such special cases by defining the font family including fallback in the custom css of the element (or on a class) - the setting in the theme styles does exactly the same.

%root% {
  font-family: "Metropolis", "Fallback Font";
}

Best regards,
timmse

3

Hi @timmse ,

Thanks for the reply!
Yes I did that as a workaround. I was just wondering why the fallback options exist in the theme settings but not on the element settings.

Nothing major, the workaround is simple enough.