We have a problem due to which we successfully implemented @ font-face for IE6-9 as usual, and in fact, everything worked fine on the client’s website in question.
Then we copied the skin to two new sites for the client (testing and production), as a result of which the font replacement still worked as expected. Over the night, SSL certificates were applied on these sites.
The next morning, it turned out that changing the font no longer worked for our annoyance. Throughout this period, the “discovery” and “torment” of @ font-face worked in everything except IE.
After I realized that all this was broken, we realized that the problem occurred only on the first page load. If you clicked on the sites menu and switched to another page with the font replaced, the @ font-face element worked as expected (IE6 and higher).
So, the question for all of you is why @ font-face doesn’t work with loading the first page, but it works great when you navigate to the specified page of the site after that?
Could this have anything to do with IE and SSL? It is possible that something is killing the IE rendering on first boot due to additional security checks that occur in the background, which are fixed by the time the user views another page on the site.
@font-face { font-family: 'BrisaAlternatesRegular'; src: url('/morph2/css/brisaalt-webfont.eot'); src: url('/morph2/css/brisaalt-webfont.eot?#iefix') format('embedded-opentype'), url('/morph2/css/brisaalt-webfont.woff') format('woff'), url('/morph2/css/brisaalt-webfont.ttf') format('truetype'), url('/morph2/css/brisaalt-webfont.svg#BrisaAlternatesRegular') format('svg'); font-weight: normal; font-style: normal;
}
internet-explorer ssl font-face pageload
Jeremy W Aug 11 '11 at 23:18 2011-08-11 23:18
source share