Hi Ryan,
I was able to reproduce a scenario in which the FontAwesome fonts were blocked due to CORS rules, but my browser seemed to automatically detect my font locally and used that font instead. It was able to display all FontAwesome glyphs without a problem. Is local('FontAwesome') redundant or is there a scenario in which it is necessary to use the local font?
On Thu, 23 Feb 2017 at 05:26 Ryan Lerch <rlerch@xxxxxxxxxx> wrote:
ryanlerchJust wondering is someone is able to review this one for me!thanks,_______________________________________________On Thu, Dec 15, 2016 at 2:14 PM, Ryan Lerch <rlerch@xxxxxxxxxx> wrote:This patch adds a final-level fallback to the FontAwesome font declaration to use the local version of the FontAwesome font.This is mainly for when devs are hacking on a local instance of apps that are using this font, as the CORS settings will resctrict them from downloading the fonts.
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
