Applying a custom `font-size` to all values exposed inside `//*[@id="advancedFonts"]` of `about:preferences#general` does not modify `font.size.monospace.x-unicode`.
Categories
(Core :: Layout: Text and Fonts, enhancement)
Tracking
()
People
(Reporter: zn7esutb, Unassigned)
References
Details
Applying a custom font-size to all values exposed inside //*[@id="advancedFonts"] of about:preferences#general does not modify font.size.monospace.x-unicode, meaning that, in an HTML5 document, I if I set lang= to one of BCP 47's special-purpose language tags inherited from ISO 639-3 (mis, und, or zxx), the font size preference is not adhered to.
This isn't intuitive, and is outside of the user's control, despite significantly affecting accessibility.
|
Reporter | |
Updated•4 months ago
|
|
||
Comment 1•4 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Layout: Text and Fonts' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Comment hidden (off-topic) |
|
||
Comment 3•4 months ago
|
||
I can't reproduce this. If I go to the Advanced font settings, choose Other Writing Systems, and change the Monospace font size, I see this reflected in font.size.monospace.x-unicode as expected.
|
|
Reporter | |
Comment 4•4 months ago
|
||
...Embarrassingly, I didn't know that that option existed. My apologies.
Description
•