Convert Fonts to config-based prefs
Categories
(Firefox :: Settings UI, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: hjones, Assigned: fterdal, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [recomp-support])
Attachments
(1 file)
The Fonts section on the General settings page under Language and Appearance should be converted to the config-based settings system. This will involve:
- A select for the default font
- A select for the font size
- A
moz-buttonormoz-box-buttonfor opening the "Advanced" settings modal
The mock ups have a "Reset" button, but this is a stretch goal and does not need to be implemented as part of this work.
Updated•9 months ago
|
| Reporter | ||
Comment 1•2 months ago
|
||
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 2•2 months ago
|
||
Comment 5•2 months ago
|
||
Backed out for causing mochitests failures in browser_search_subdialogs_within_preferences_5.js.
[Backout link]https://hg.mozilla.org/integration/autoland/rev/4f599c25538f)
Comment 7•2 months ago
|
||
| bugherder | ||
Comment 8•1 month ago
•
|
||
Verified through exploratory testing that the functionality of the Fonts section remains unchanged after the landing of this patch, with browser.settings-redesign.enabled both enabled and disabled. However, I found an issue for which I have logged Bug 2019296.
Testing was performed on Windows 11, Ubuntu 24.04, and macOS 15 on Nightly 150.0a1 and Firefox 149.0b1.
More thorough testing will be conducted once the Accessibility page is finalized and the new Fonts section is integrated there.
@Finn, @Hanna
I also have a few UI-related questions. In the Figma document added in Comment 1, the two select controls for “Default font” and “Size”, as well as the “Advanced…” button, are labeled differently: “Font family”, “Font Size”, and “Advanced settings”.
Is this change in naming expected, or has the UI design been updated since then?
Updated•1 month ago
|
| Reporter | ||
Comment 9•1 month ago
|
||
Hi Simona, thanks for the thorough testing! We'll want to switch to the strings shown in Figma eventually, but we can do that level of polish when we handle moving everything to the new "Accessibility" page. I don't think we need a separate bug for that at this time.
Description
•