font-family: icomoon;
   src: url(fonts/icomoon.eot);
   src: url(fonts/icomoon.eot#iefix) format('embedded-opentype'), url(fonts/icomoon.ttf) format('truetype'), url(fonts/fonts/icomoon.woff) format('woff'), url(fonts/icomoon.svg#icomoon) format('svg');
   font-weight: 400;
   font-style: normal

 font-family: "icomoon";
 font-style: normal;
 font-weight: 400;
 src: url("moz-extension://8eaa4596-3cd0-4168-bee4-6708c37d8684/fonts/icomoon.ttf?gbkn1h") format("truetype"), url("moz-extension://8eaa4596-3cd0-4168-bee4-6708c37d8684/fonts/icomoon.woff?gbkn1h") format("woff"), url("moz-extension://8eaa4596-3cd0-4168-bee4-6708c37d8684/fonts/icomoon.svg?gbkn1h#icomoon") format("svg");

Hi, There is an issue with icomoon fonts with the new Firefox. Firefox seems to be ignoring the actual glyphs and replacing them with some other (maybe built-in) icons. This problem wasn't existent before the big Firefox update. You can see this in the screenshot attached (icons on the top right were supposed to be social network icons e.g. facebook instagram etc.) The web page mentioned is accessible at http://ordaf.org/ The problem is about the url of the font file being altered. Here's the font-face css code for the web page: @font-face { font-family: icomoon; src: url(fonts/icomoon.eot); src: url(fonts/icomoon.eot#iefix) format('embedded-opentype'), url(fonts/icomoon.ttf) format('truetype'), url(fonts/fonts/icomoon.woff) format('woff'), url(fonts/icomoon.svg#icomoon) format('svg'); font-weight: 400; font-style: normal } And this is what I get on the developer tools: @font-face { font-family: "icomoon"; font-style: normal; font-weight: 400; src: url("moz-extension://8eaa4596-3cd0-4168-bee4-6708c37d8684/fonts/icomoon.ttf?gbkn1h") format("truetype"), url("moz-extension://8eaa4596-3cd0-4168-bee4-6708c37d8684/fonts/icomoon.woff?gbkn1h") format("woff"), url("moz-extension://8eaa4596-3cd0-4168-bee4-6708c37d8684/fonts/icomoon.svg?gbkn1h#icomoon") format("svg"); } Looking forward for a workaround for this, since the webpage is owned by me and I faced this problem with some other pages I've been working on.