> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/faq/theme-setup/fonts-not-displaying-in-safari-or-firefox.md).

# Fonts not displaying in Safari or Firefox

The initial Avante v14.0.0 release had a CSS error that made fonts revert to defaults in Safari and Firefox. It was fixed later in v14 — update the theme.

On the initial **v14.0.0** release, fonts could revert to system defaults in Safari and Firefox while still looking correct in Chrome — headings and body text lost the fonts set in Theme settings.

{% hint style="success" icon="circle-check" %}
**This was fixed in a later v14 release.** Every version from that patch onwards, v16 included, is unaffected. If your store still shows it, it is running the original v14.0.0 files.
{% endhint %}

***

### How to check if you're affected

Open your store in **Safari or Firefox** and compare it with Chrome. If the fonts look generic or unstyled in those two browsers only, you're affected.

Then check your theme version in **Shopify Admin → Online Store → Themes** — the version number is shown under the theme name. If it reads **14.0.0**, that's the cause.

***

### Why this happens

Avante v14 introduced scalable fonts built on `rem` units. In the initial release, the font size calculations in `snippets/font-variables.liquid` divided by a value carrying a `px` unit, which is not valid CSS.

Chrome accepts it silently. Safari and Firefox follow the spec strictly and discard the whole rule, so every font variable stops applying at once. That is why the problem looks like "all fonts are gone" rather than one heading being off.

***

### How to fix it

**Update Avante to the current version.** The corrected `font-variables.liquid` ships with every release after the v14 patch, so updating replaces the broken file and the fonts come back with no further steps.

{% hint style="info" %}
If updating isn't an option right now — for example, you have customizations in the theme code that aren't merged yet — [**contact our support team**](https://staylime.zendesk.com/hc/en-us/requests/new) and we'll patch the single file on your current theme instead.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/faq/theme-setup/fonts-not-displaying-in-safari-or-firefox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
