Timeline for We are switching to system fonts on May 10, 2021
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 12, 2021 at 17:59 | comment | added | Prid | Chrome extension to revert fonts (and other changes): chrome.google.com/webstore/detail/revert-stackexchange-form/… | |
| May 25, 2021 at 9:08 | comment | added | rustyx | Use this answer which is based on the Stylus browser plugin (very powerful). | |
| May 12, 2021 at 17:49 | comment | added | Peter | @AaronShekey This font change introduces difficulty for me to read the text on stack websites, specifically, the monospace font used on windows for syntax highlighting looks fat and is hard to read, the segue ui font as others have commented, looks like a comic sans-inspired design. Why isn't this an option for users to decide to use? | |
| May 12, 2021 at 2:39 | comment | added | Andrew | @AaronShekey they look better to you on high DPI and 1x screens. How good things look, and comparative judgements are subjective. There are a lot of issues that have been overlooked, people with bad eyesight like Nick here having issues with the font, the change in base font size itself being a problem, possible issues for the dyslexic, etc. | |
| May 11, 2021 at 11:04 | comment | added | BoltClock's a Unicorn | On my machine, Firefox is inconsistently rendering the text using grayscale anti-aliasing versus subpixel anti-aliasing depending on the SE site you're on. For example, it's grayscale on Meta SO, but subpixel on SO and MSE. It's truly bewildering considering the CSS is the same. Subpixel is always used on Edge and Chrome. WPF ClearType lets you configure this; there isn't a standardized equivalent in CSS yet. | |
| May 11, 2021 at 10:46 | comment | added | Kobi | Yeah, the Windows monospace font looks bold and blurry. | |
| May 11, 2021 at 10:12 | comment | added | binaryfunt | A lot of these complaints just seem to be a problem with Firefox? I use Edge, and loaded up Firefox to compare and the text rendering across the board in FF just looks worse (1080p, 100% scaling). Also perhaps because Segoe UI is slightly thinner than Arial? | |
| May 11, 2021 at 9:29 | comment | added | Thorbjørn Ravn Andersen | The new Windows fonts are too small for me. I'd like to go back too. Also the focus should have been on readability , not UI. | |
| May 10, 2021 at 22:02 | review | Suggested edits | |||
| May 10, 2021 at 22:17 | |||||
| May 10, 2021 at 18:18 | comment | added | leonheess | Custom Fonts User Script: Revert the Font Updates | |
| May 10, 2021 at 17:14 | comment | added | SuperStormer | Here's a userstyle that fixes both sans and monospace (and hardcoded code block fonts) gist.github.com/SuperStormer/60a5e5c7e9549e9ed865a579df6f11be | |
| May 10, 2021 at 17:13 | comment | added | Rory Alsop | As a (slightly) older person, I have to say Segoe is much harder to read than Arial, which has always been incredibly clear for me. I'm now going to have to go and figure out a way to reset my fonts back to ones I can read without getting a headache :-( | |
| May 10, 2021 at 17:13 | comment | added | Patrick Roberts |
Here's a UserScript I just threw together, adjust the @match to taste: gist.github.com/patrickroberts/3b3a89cb38c94c8eb591443e329cc768 click the "Raw" button to automatically prompt installation if you already have Tampermonkey/Greasemonkey.
|
|
| May 10, 2021 at 17:03 | comment | added | SuperStormer |
From the wayback machine: body{--ff-sans:Arial,"Helvetica Neue",Helvetica,sans-serif;--ff-serif:Georgia,Times New Roman,Times,serif;--ff-mono:Consolas,Menlo,Monaco,Lucida Console,Liberation Mono,DejaVu Sans Mono,Bitstream Vera Sans Mono,Courier New,monospace,sans-serif;}
|
|
| May 10, 2021 at 17:02 | comment | added | Patrick Roberts | I can live with most of the changes, but reading comments specifically (whatever the system-ui default is for Windows at 13px) is straining my eyes, so I'll be reverting to the old font stack with a userscript as well until this is addressed. | |
| May 10, 2021 at 17:01 | comment | added | Aaron Shekey StaffMod | @Nick Our intent with the system font switch is that they look better on high DPI and 1x screens. I use both throughout my day. | |
| May 10, 2021 at 16:59 | comment | added | Nick is tired | @AaronShekey Having a play around with multiple settings, I think my biggest issue is, it feels like this change hasn't taken into account high DPI devices, it looks... okay I guess?, while running at 200% scaling in 4K, but any less than that is extremely uncomfortable, and I have no intention of using my screen at 200% scaling, ta for CSS heads up | |
| May 10, 2021 at 16:58 | comment | added | Zoe - Save the data dump | @samcarter_is_at_topanswers.xyz github.com/openstyles/stylus | |
| May 10, 2021 at 16:54 | comment | added | samcarter_is_at_topanswers.xyz | @AaronShekey Any chance to get a user script to change the font? | |
| May 10, 2021 at 16:53 | comment | added | Aaron Shekey StaffMod |
This is our plan going forward. I would recommend sitting with these changes for more than 5 minutes, but I hear ya. If you're comfortable writing your own CSS, you can override the --ff-sans variable to have our old font stack which is Arial, "Helvetica Neue", Helvetica, sans-serif.
|
|
| May 10, 2021 at 16:47 | comment | added | 41686d6564 | Related. | |
| May 10, 2021 at 16:45 | history | answered | Nick is tired | CC BY-SA 4.0 |