Open
Bug 1933004
Opened 1 year ago
Updated 1 year ago
browser.display.use_document_fonts vs generic-family inconsistencies
Categories
(Core :: Layout: Text and Fonts, enhancement)
Core
Layout: Text and Fonts
Tracking
()
NEW
People
(Reporter: thorin, Unassigned)
Details
Attachments
(1 file)
|
92.51 KB,
image/jpeg
|
Details |
In testing I have found that browser.display.use_document_fonts = 0 behaves inconsistently with <generic-family>.
It seems as if monospace, sans-serif and serif are never blocked (I would need to flip to a language that isn't default serif to confirm), but others such as cursive, fangsong and system-ui are
I found an old issue from 24 years ago :) ... Bug 79074 with other linked issues, but whatever the logic from then is no doubt mostly obsolete now. Since then we've had new generic families, and maybe this needs a reassessment and tidy up? If not, then feel free to close as invalid
My intuition says we should block "fonts", not generic families
| Reporter | ||
Comment 1•1 year ago
|
||
https://arkenfox.github.io/TZP/tests/fontdebug.html
1 0
MS Shell Dlg \32 tahoma times new roman (expected)
cursive comic sans ms times new roman
fangsong fangsong times new roman
monospace consolas consolas
sans-serif arial arial
serif times new roman times new roman (serif is my default font)
system-ui segoe ui times new roman
You need to log in
before you can comment on or make changes to this bug.
Description
•