Does 2.3 use tracking fonts?
-
I upgraded to 2.3 last night and noticed that uBlock Origin (Firefox Add-on) was blocking all of the new GUI icons that are now font characters instead of images. Does the new web interface pull in a typeface font from an external site or load it from the firewall's file system?
-
I forgot to check in the logging tab for uBlock Origin where the fonts are loaded from before reinstalling 2.2.6 .
-
They're on the firewall (/usr/local/www/css/fonts/ and /usr/local/www/vendor/font-awesome/fonts/)
-
You most likely have a 3rd party plugin. uBlock shouldn't block with a default install.
-
I have uBlock Origin configured to block ALL remote fonts.
When I migrate to 2.3 I can easily whitelist the fonts on the pfSense hosts in uBlock Origin. -
The fonts are hosted locally on your pfSense box. Your config might be too aggressive.
edit: guess it depends on the viewpoint of "remote". If you mean remote of your PC then yes you'll have to whitelist.
-
'remote' is uBlock Origin's term for anything not found on the host that is running the browser.
My config isn't aggressive, it's just safe. -
By that definition they aren't remote, therefore the config is aggressively blocking things that aren't remote. Or something else is blocking it that you haven't caught yet (other people had issues with 3rd party plugins for uBlock).
edit: misread "host that is running the browser" as basically "host that is running the webpage". my bad.
-
The fonts are not stored locally on my workstation, they are remotely stored on another host, the firewall.
uBlock is working fine for me. It's doing exactly what I expect (and want). I don't have a problem with it.
-
I had one of my pfBlockerNG beta testers run into this issue, when UBlock was blocking a FA icon.
Info here:
https://github.com/chrisaljoudi/uBlock/issues/428
https://github.com/gorhill/uBlock/issues/15
