Hello. Your latest design for www.bungie.net features use (and UTF abuse ;) of glyph/icon fonts in the menu bar instead of the old images (most notably for notification bell and search magnifier). This is not the only custom and remote font your are using. There are also for example fontbungle, and FontAwesome... but there is a difference in how Material Icons font was implemented compared to the other two. Mozilla Firefox for example has always allowed users to block websites from choosing their own fonts, so that they wouldn't have to suffer reading pages in Times when they wanted Verdana and nothing else... This was there way before remote/downloadable fonts. Setting is in the preferences, but it can also be accessed as the config key: "browser.display.use_document_fonts" Once designers started using font icons Mozilla Firefox implemented another config key: "gfx.downloadable_fonts.enabled" so that even in cases where users are refusing to allow web pages to choose their own font they would still get the remote font icons loaded. Which finally brings me back to how Material Icons font is used on www.bungie.net. Fonts like fontbungle and FontAwesome are defined in your stylesheet as remote fonts only (src: url...) but Material Icons font is defined as either a system or remote font, which breaks the display of font icons for users that prevent pages from choosing their own fonts. Excerpt from your stylesheet: [quote] src: local("Material Icons"), url("/fonts/MaterialIcons-Regular.woff2") [/quote] I don't know who is in the wrong here. Browsers for not having this handled better, CSS designers for abusing standards... All I know is it's very ugly to see "notifications_none" across half of the menu bar every time I visit www.bungie.net.