So I added the Monty fonts just in CSS, which makes sense why they don’t work on other browsers.
How exactly can I add them again so they work in Safari using your answer above? Sorry I’m still relatively new to Bubble! Any guidance would be most appreciated
So i originally downloaded the fonts into otf and ttf, then transferred them into a CSS file converter online. This is what the CSS Bold Font file I uploaded looks like.
Ah ok so I also did take the CSS files and upload them all using the text editor feature, then uploaded them 1 by 1 into Bubble (attached a screengrab). So they are in my Bubble App, work fine in Chrome, just not Safari.
So would following the steps in the manual still fix it so they would show on Safari?
any luck here? I’m having the same problem with safari and mobile more generally. Nexa Bold is not showing up at all and is being replaced by another font.
I attempted to upload the multiple font types to the file uploader and then use that link to host the font in my bubble app. Below is a screenshot of my CSS file:
Maybe Nexa Bold is just too uncommon of a font? Any advice by the community would be appreciated. You can test it here at https://www.bookwithrove.com. It works on google chrome (web) but almost no where else.
“Too uncommon” shouldn’t be a factor if the fonts are uploaded and hosted on the same server that hosts all the other assets for the site.
I also uploaded custom fonts following the Bubble instructions, and I am also having issues on iPhone using both Chrome and Safari browser.
I have 5 custom fonts, 4 of which are ttf and one of which is otf. I have font forge, so I can probably convert to whatever format might solve this if anyone has any suggestions?
Custom fonts are essential for my web app. Part of my company’s brand identity is 2 fonts that we designed. Our fonts function as a brand mark, and the design can’t be complete without them.
I had this exact issue having followed another (much older) forum post which went something like this. Here’s my solution for anyone who drops on this page
I didn’t have the same font in older font file types, I also discovered it generally wasn’t required for modern browsers, but what you did need to do for Safari was to specify what type of font file it is. I don’t think font-weight etc are needed. The format parameter is key.
For me it wound up being the CSS file formats. Something was slightly off with the formatting in mine because I was doing them in a text editor, saving as text, and then changing the extension on the file afterwards.
Once I did them in a proper CSS editor it was resolved.
It got tricky because there wasn’t an error message on my end. The interface didn’t give any indication that the CSS files weren’t functioning.