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. 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?
Bug 1972365 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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?