Icons are broken with standard font set.

[louipc]

The issue is already well described here: uBlock-LLC/uBlock#1181
Commits to fix are here: uBlock-LLC/uBlock@a947537...53768af

[BigDaddyLinux]

Can anybody explain this for the non tech guy. Is this issue going to be fixed in an upcoming release? I do not personally have this issue but a family member does have the broken icons and I have no idea how to fix it.
any help is appreciated.

[gorhill]

The extension's package contains FontAwesome font file, this is used to render various icons used in uBlock. Using a font for icons simplifies a lot maintenance. However the --disable-remote-fonts flag also affects local fonts (not just the remote ones as the name of the flag implies), and this prevents the FontAwesome font file (which is local, part of uBlock package) from being loaded by uBlock, and as a result, no icons in the UI.

[BigDaddyLinux]

Thank you for the explanation. The only question I have is, Is there something I can do on my end to fix it or do we need to wait for it to be fixed in an upcoming release?

[gorhill]

I don't know of anything else which can be done other than not using --disable-remote-font. I don't plan to release a fix for this in the next release, because that would delay unduly the release to the next week end at earliest. You could install chrisaljoudi/uBlock repo, it has the fix.

[BigDaddyLinux]

I thank you for your patience in explaining it. I would rather continue using your releases.
Where Is The --disable-remote-font setting? Is that in ublock or in firefox itself?
How do I not use it

[gorhill]

You can toggle the flag in about:config (Firefox), as explained here (with further instructions for Chromium).

[ghost]

This user style allows the user to only use a font they want while allowing font awesome to work. It requires Stylish of course.

https://userstyles.org/styles/112439/disallow-web-page-fonts-except-fontawesome-et-al

Third party fonts are a potential privacy issue. I'm uncertain if the user style could address this. If the desire to use a specific font is driven by aesthetics then the user style should be a nice work around.

Fanboy's Anti-thirdparty Font list addresses the privacy issue to an extent. Fwiw, IceCat, the GNU version of Firefox is pretty keen on disabling fonts out of the box.

[louipc]

On Fri 17 Apr 2015 09:42 -0700, FrankNitty wrote:

Thank you for the explanation. The only question I have is, Is there
something I can do on my end to fix it or do we need to wait for it to be
fixed in an upcoming release?

It's patched in the latest beta release of the chrisaljoudi maintained ublock.
https://github.com/chrisaljoudi/uBlock/releases/tag/0.9.3.5-beta.2

[BigDaddyLinux]

thank you all for your help and your hard work on the addon itself

[chrisaljoudi]

#154 addresses this.

[gorhill]

[RoxKilly]

deleted.
[Just realized I should have opened a new issue. See #359]

[louipc]

That is a nice feature but it doesn't address the bug.
The interface is still broken when using standard font set.
Is this a won't fix?

[gorhill]

It does fix the bug for people who wanted to disable remote fonts (as reported in the original issue). If your goal is to force web page to use a specific font, I consider this a Firefox issue.

[louipc]

Not strictly a firefox issue. The interface breaks in chromium as well when launching with --disable-remote-fonts. Would be nice if it didn't break. Please reopen if you're open to solutions/ideas. thanks!

[gorhill]

The interface breaks in chromium as well when launching with --disable-remote-fonts

That's the point of the fix, to not use --disable-remote-fonts and to let uBlock do the blocking of remote fonts instead -- with ability to do it on a per-site basis as an extra.