You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IE is not recognizing the custom font, and instead defaulting to one of the fall backs (arial, I think).
Edit: I looked into this, my findings and passing the baton:
Nothing jumped out at me as an issue.
Our webpack config is pretty up to date, and includes the css autoprefixer plugin that usually solves IE compatibility issues with css. Our custom font works in all browsers including Edge, just not IE11. I was unable to figure out the source of our font (i.e. is it a Google font?).
We include all font file versions (.eot is the format that IE11 requires) and import them correctly (@import(...)).
IE is not recognizing the custom font, and instead defaulting to one of the fall backs (arial, I think).
Edit: I looked into this, my findings and passing the baton:
Nothing jumped out at me as an issue.
Our webpack config is pretty up to date, and includes the css
autoprefixer
plugin that usually solves IE compatibility issues with css. Our custom font works in all browsers including Edge, just not IE11. I was unable to figure out the source of our font (i.e. is it a Google font?).We include all font file versions (
.eot
is the format that IE11 requires) and import them correctly (@import(...)
).In my research I came across a new setting in Windows 10 that blocks suspicious font downloading, but I've dispelled this idea by confirming fonts will don't work on IE11 on Windows 8.1 on Browserstack. https://docs.microsoft.com/en-us/windows/security/threat-protection/block-untrusted-fonts-in-enterprise#Turn_on_and_use_the_Blocking_untrusted_fonts_feature
I did not get time to evaluate this potential clue: facebook/create-react-app#4121
The text was updated successfully, but these errors were encountered: