Hi all,
Not sure if this is useful for anyone, but thought it might be worth mentioning in case. We use fontawesome in our html output and wanted to upgrade to use v6. We host it ourselves as per https://fontawesome.com/docs/web/setup/ ... f/webfonts, using a master page to reference the fontawesome css file stored in our project. We noticed the icons not displaying after we added in the v6 files and referenced them from the master page.
It seems that disabling a setting in the target called Resolve CSS variables (required for IE compatibility) resolved the issue, not completely sure why. Obviously, disabling this might have an impact if you are using css variables and you need to support output on IE.
thanks,
mark
fontawesome v6 in html output
Re: fontawesome v6 in html output
In case it helps, the release notes for Fontawesome v6 Beta 3 indicate support for IE as been removed.
https://fontawesome.com/docs/changelog/
Version 6 will no longer support Internet Explorer
We have ended support for Internet Explorer in v6 - all IE specific fallbacks and assets have been removed. As always, you can view the official list of browsers that Font Awesome supports. https://fontawesome.com/docs/web/dig-de ... er-support
https://fontawesome.com/docs/changelog/
Version 6 will no longer support Internet Explorer
We have ended support for Internet Explorer in v6 - all IE specific fallbacks and assets have been removed. As always, you can view the official list of browsers that Font Awesome supports. https://fontawesome.com/docs/web/dig-de ... er-support
Re: fontawesome v6 in html output
If you use the setting Resolve CSS variables (required for IE compatibility), then Flare looks for CSS variables in any of your source stylesheets, and during the build it will replace all the CSS variables with actual values in the output stylesheet.
Or at least that's the idea - in practice it breaks quite easily unless you use very simple CSS variables, and can replace the CSS variables with a blank. It also breaks if you try to use CSS variables in any skins.
For my projects, I never use that setting, and manually write CSS to support IE - insert a line with the actual value (for IE), followed by a duplicate line with CSS variable.
Anyway, I would guess that Flare is finding the fontawesome CSS in your project, and has tried to replace any CSS variables with actual values, and probably broken it in the process.
Or at least that's the idea - in practice it breaks quite easily unless you use very simple CSS variables, and can replace the CSS variables with a blank. It also breaks if you try to use CSS variables in any skins.
For my projects, I never use that setting, and manually write CSS to support IE - insert a line with the actual value (for IE), followed by a duplicate line with CSS variable.
Anyway, I would guess that Flare is finding the fontawesome CSS in your project, and has tried to replace any CSS variables with actual values, and probably broken it in the process.