www.wysiwygwebbuilder.com

Version 14-7-19 64bit dutch.
Strange things happen after update with the fontawesome published as font in Firefox, just see a rectangle with letters in it.
When I publish this in chrome it shows.
I stumbled on this when I opened my file that was oke and showed everything as it should be, but now with firefox
I have this problem.
Also other files wbsfiles which are using a fontAwesome symbol have this problem in firefox now.
I'm pretty sure a few updates before 14-7-19 this problem didn't exist! because I checked al my files!
https://ufile.io/iqnsjckq here is a wbs to inspect

Does it still work in WB14?
Maybe you have installed an update of FireFox which broke this functionality?

If it still works in WB14, do you see any differences in the generated code?

Firefox had an update. But on my original site the fontawesome shows the right way with the same firefoxbrowser.
I noticed that on my website if I look at the used fonts it shows Fontawesome but now it shows at the used fonts
Times New Roman the class of the icon is the same.

Does the problem also occur when you published the website?
Or is it only in local preview?

I think it's a bug in the FireFox update.

It looks like FireFox has a bug in local font processing:

This workaround may fix the issue:
http://testingfreak.com/how-to-fix-cros ... me-and-ie/

I uploaded the page with the icons and it shows the correct preview, also on my wampserver it shows the right way.
So I has to be in preview only that the problem occurs.
So no failure of your programme but due to firefox local preview!

I too have seen this with FontAwsome in FireFox since this update, but HERE'S MORE: PDF files (linked as file) will not show, although they do in Chrome and they used to in FireFox.

Just a warning to everyone...

Did you apply the 'fix'?

http://testingfreak.com/how-to-fix-cros ... me-and-ie/

https://support.mozilla.org/bm/questions/1264762
Above the answer of support Mozilla.
They let you change the privacy.file_unique_origin preference to switch the value from true to false
instead of security.fileuri.strict_origin_policy as mentioned at testingfreek.com.

And here https://developer.mozilla.org/nl/docs/W ... estNotHttp
you can read that it has to be the privacy.file_unique_origin preference that has to be changed.