Justin Khoo The reason why we see erratic cases of fonts sometimes still rendering in Times New Roman (TNR) even though precaution is taken to not load the font in Outlook is because Outlook caches @font-face declarations (until app restart). Normally, if you hide the @font-face declaration from Outlook, you can refer to custom fonts inline and Outlook will fallback to the next declared font such as Arial because to Outlook, the font 'doesn't exist'. However if another email uses the same custom font but DOESN'T hide the @font-face declaration (or @import or linked stylesheet), then Outlook caches that declaration and will cause subsequent uses of the font to render in TNR. This is all due to the fact that Outlook seems to process @font-face declarations but fail to load the font for some reason and causing it to treat the declared font as TNR. Front-End Dcode Hi Camilo, I didn't have an outlook desktop app to test, so I just rely on litmus client testing.

Best games for mac on itunes. ($5) features one of the most wonderfully bizarre premises in gaming: You play an octopus posing in suburbia as a human father, with a human wife and human kids.

This issue may happen if the sender uses a font that is not installed on your Mac. Please also try to copy the signature from the original email, paste to the reply message, and then reply to yourself to see if the font keeps changing.

Can I get more informations about your feedback? I really like to know if I can rely on this trick. Where you able to test this on a true native app?

I did launch an 'obvious' test on litmus (everybody can recognise this dear 'Comic Sans MS'): • It seems to work because: 1. Baloo Tamma is used where web fonts is supported 2.

Comic Sans ms where it's not (No 'Times New Roman' on outlook) 3. Or else sans-serif • also add a check for the!mso conditional comment Thanks for your feedback. Update: There's the same test without conditional comment above link to google font.