Hi Erica,
you can see your font in one of the browsers because you’ve used it to select the font and Chrome cached this font.
The problem with other browsers /devices is that browsers do not know where to get this font from.
Yes, you’ve made edit to your aErikaCustom.css to define proper font-face:
/*FONT STYLING */
@font-face {
font-family: 'NebuihRegular';
src: url('{{'NebuihRegular.woff2' | asset_url }}') format ('woff2'),
url('{{'NebuihRegular.woff' | asset_url }}') format ('woff'),
url('{{'NebuihRegular.ttf' | asset_url }}') format ('truetype'),
url('{{'NebuihRegular.otf' | asset_url }}') format ('opentype'),
font-weight: normal !important;
font-style: normal!important;
font-display: swap !important;
}
h1, h2, h3, h4, h5, h6, header {
font-family: 'NebuihRegular'!important;
}
However, as shown above I can see unprocessed liquid instead of url(s).
If your asset has**.css** extension Shopify would not process any liquid inside, you must rename your asset to be .css.liquid for this. This is kinda discouraged by Shopify, and modern themes define font-faces somewhere in layout, inside (this also has benefit of being processed ASAP for less FOUC).
But as a quick fix, try to simply rename your custom stylesheet asset file to .css.liquid
Also, you have another definition for this font in base.css which is not good and difficult to debug if there are duplicate definitions. Anyway, the code in base.css could work if your font files were uploaded to your theme’s assets/ folder, however, I believe they are uploaded to your store settings-> files area, right?
In this case the liquid code above should use file_url filter instead of asset_url