Now, in Preferences / Appearance / Fonts, the "Allow documents to use other fonts" option disallows all font specifications, including both generic: font-family: sans-serif; and specific: font-family: helvetica; What would be more useful is the ability to differentiate between these cases, so the user can disallow specific font settings but still allow the stylesheets to use generic settings. These generic settings would then resolve into the specific font families configured by the user on the same preferences page. So, this option should be broken into two, one for generic font types and the other for specific font families. Given that most people provide both alternatives in their stylesheets, as in font-family: helvetica, sans-serif; leaving only generic settings enabled would result in most pages looking acceptably close to the page author's intention, at the same time protecting the user from rigid no-fallback specifications that refer to fonts which are not well suited for browser display. And by the way, to be consistent, the settings for everything except serif and monospace should be grayed on that page if the generic font types (or all document font settings, as now) are disallowed because they would never have any effect anyway.

.

See also bug 105297.

What about implementing this via bug 56441 ("Need font banning") ? I consider to implement that RFE via accept/deny regex filters... any suggestions ?

This is totally and completely unrelated.

David Baron wrote: > This is totally and completely unrelated. Really ? See comment #0: -- snip -- What would be more useful is the ability to differentiate between these cases, so the user can disallow specific font settings but still allow the stylesheets to use generic settings. -- snip -- My idea was to filter the CSS font spec and allow or disallow fonts per regex filters... ... or would a regex-based mapping system (e.g. ".*times.*" --> "new times") better here ?

This bug is specifically about allowing generic fonts but not anything else.

Anyway, this is a duplicate. Please do NOT carry the regex discussion over. *** This bug has been marked as a duplicate of 79074 ***

vrfy dupe