Open
Bug 1433053
Opened 7 years ago
Updated 3 years ago
(Dis-)Allow custom website fonts on a per-site basis
Categories
(Core :: Layout: Text and Fonts, enhancement, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: heavymetal, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20180118215408
Steps to reproduce:
Firefox has a setting to (dis-)allow websites the use of custom fonts. However, this general setting applies to ALL websites, which is becoming more and more impractical nowadays. Many sites use custom fonts to include their icons, so in general, custom fonts are a necessary evil. But some sites use really ****, blurry fonts, which render a site simply unreadable. Even worse, some sites embed BROKEN fonts and don't render most of the text at all. See https://www.waz.de/ as a very bad example. With custom fonts enabled, all menu items, headlines and comments are just missing.
Actual results:
Some sites are useless with custom fonts enabled, some are useless with custom fonts disabled.
Expected results:
Firefox should allow enabling/disabling custom website fonts on a per-site basis instead of offering a global setting only.
Updated•7 years ago
|
Severity: normal → enhancement
Component: Untriaged → Layout: Text
Product: Firefox → Core
Comment 1•7 years ago
|
||
Is this something an add-on could do, rather than having to be built in to the browser itself?
Comment 2•7 years ago
|
||
(In reply to heavymetal from comment #0)
> Even worse, some sites embed BROKEN fonts and don't render most of the text
> at all. See https://www.waz.de/ as a very bad example. With custom fonts
> enabled, all menu items, headlines and comments are just missing.
That site seems to work fine for me, with custom fonts either enabled or disabled, which suggests you may be a different problem there (separate from the feature request for a per-site setting).
Do any error messages appear in the Web Console if you have it open when loading the site with broken fonts?
Updated•7 years ago
|
Priority: -- → P5
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•