111

TL;DR We’re shipping system fonts as our default font stack. We plan to do this on May 10th, 2021.

What?

We’re planning on specifying system fonts on Stack Overflow and the Stack Exchange Network. On macOS and iOS, you’ll see things set in San Francisco. On Windows, you’ll see Segoe. On Android you’ll get Roboto. Ubuntu will show, well, Ubuntu. We’ll also use their monospace equivalents when writing in code or rendering keyboard keys.

OS Sans Mono
macOS San Francisco San Francisco Mono
iOS San Francisco San Francisco Mono
Windows Segoe UI Consolas, or Cascadia Mono, Segoe UI Mono if you've installed those manually
Ubuntu Ubuntu Ubuntu Mono
Android Roboto Roboto Mono
Chrome OS Roboto Roboto Mono
Fallback sans-serif Menlo, Monaco, Consolas, monospace

We’re leaving serif fonts alone so those will stay as Georgia, Cambria, Times New Roman, Times, and then serif as a fallback. We really don't do much with serifs anyway, and we don’t want to mess with the themes that rely on them.

Here’s the exact font stack we’ve specified that’ll go live on the 10th.

@ff-sans:
    system-ui, -apple-system, BlinkMacSystemFont, // San Francisco on macOS and iOS
    "Segoe UI", // Windows
    "Ubuntu", // Ubuntu
    "Roboto", "Noto Sans", "Droid Sans", // Chrome OS and Android with fallbacks
    sans-serif; // The final fallback for rendering in sans-serif.
@ff-serif: Georgia, Cambria, "Times New Roman", Times, serif;
@ff-mono:
    ui-monospace, // San Francisco Mono on macOS and iOS
    "Cascadia Mono", "Segoe UI Mono", // Newer Windows monospace fonts that are optionally installed. Most likely to be rendered in Consolas
    "Ubuntu Mono", // Ubuntu
    "Roboto Mono", // Chrome OS and Android
    Menlo, Monaco, Consolas, // A few sensible system font choices
    monospace; // The final fallback for rendering in monospace.

Why?

Mark Otto put it really well on his personal blog, documenting GitHub’s rationale for switching. Like GitHub, our original font stack used Arial across macOS, iOS, and Windows. Arial was first created in 1982, and has served the web well for decades. But technology moves on. Modern system typefaces look better on both new high DPI screens, and old screens alike. Apple’s San Francisco and Microsoft’s Segoe both look great on retina displays, have more expressive weights, and improve readability across all contexts. With more weights, we can have better hierarchy. We can also get more expressive. For example, in dark mode, we could drop our font weights a bit for better readability.

But what about consistency?

We originally chose Arial because it was available on the widest set of devices, allowing us to have a consistent experience wherever you were. However, Arial doesn’t ship with Linux distros or Android devices. We’re currently only achieving consistency between macOS, iOS, and Windows, leaving 2 platforms to choose their system font. We’d rather have the consistency be shifted to the device itself—when viewing Stack Overflow on iOS, it’ll feel that much more native in San Francisco. Same with Android, which is already being displayed in Roboto.

We should also note that prior to these changes, our monospace font stack varied wildly. Now you'll have better consistency between sans and monospace, since we'll do our best to choose the right pairings.

Will my Stack Exchange site lose its custom font?

Nope! This change will not affect sites that have their own typefaces. Sites like Christianity and English will still be displayed in their custom fonts.

Future possibilities

If consistency were the absolute goal, we’d ship our own custom font. I would love to be able to truly express our brand through a typeface, but that means users would have to download custom fonts and wait for them to display. We’d also have to cover international character sets. Displaying custom fonts is getting more realistic every day at our scale, so we may revisit that choice at some point, and come back to a more consistent experience. System fonts let us modernize in the meantime without too many drawbacks.

Also, since a lot of our site is built using our design system, we can store these font stacks as CSS variables. We could allow users to more easily specify dyslexia-friendly typefaces, or load their own entirely.

Some screenshots

Safari on macOS Safari on macOS

Firefox on Windows Firefox on Windows

Firefox on Ubuntu Firefox on Ubuntu

So what now?

When this change drops, we could use your help in discovering any bugs—things like unexpected alignment, or any questionable bits where we clearly got the wrong typeface.

42
  • 59
    Hopefully this will prevent issues like 'pom’ getting mistaken for ‘porn’ in the future. – ColleenV 2 days ago
  • 2
    @DavidPostill "We’re planning on specifying system fonts on Stack Overflow and Stack Exchange" (and more in the post) suggests that this is network wide – caird coinheringaahing 2 days ago
  • 2
    @DavidPostill This change is global, affecting the whole network. If your network has the default font, that'll change on the 10th. – Aaron Shekey 2 days ago
  • 8
    @ColleenV rnicrosoft.com ;) – Ollie 2 days ago
  • 9
    Which one of y'all is gonna write a script to put a space in between any r's and n's 😛 – Aaron Shekey 2 days ago
  • 14
    Would still be nice if all the fonts made the difference between l and I (bonus points for not noticing which is which) substantially more noticeable, at least along the lines of what the Ubuntu font does. – Zoe the 1337 Princess yesterday
  • 2
    @Zoethe1337Princess I emphatically agree, but alas, here we are. This is the quickest, least bytes-over-the-wire way we can get to more modern fonts. – Aaron Shekey yesterday
  • 7
    A welcome change as long as it doesn't break Tony the Pony.;-) – Jon Ericson yesterday
  • 1
    @Chindraba ... Really confused why dark mode has anything to do with font choices. – Catija yesterday
  • 2
    Not related directly, just if they're gonna tweak CSS across the board, adding the CSS for dark mode at the same time might be less of a burden. Or not. Just asking? – Chindraba yesterday
  • 1
    The waiting continues. How about the bulk of the comment, before mention of dark mode? – Chindraba yesterday
  • 4
    @Milliways - San Fransisco is not a user font, it's a system font. As such it doesn't appear in Font Book etc. Initially, Apple kept a tight license on it, meaning it could only be used for Apple product mockups etc, but they seem to have relaxed that in recent times. You can download it if you need it as a user font, but you don't need to for it to display correctly - developer.apple.com/fonts – Tetsujin yesterday
  • 8
    What about non-ubuntu linux? – Aconcagua yesterday
  • 2
    @ErkinAlpGüney So would our marketing designers. You'll notice our marketing pages are set in Source Sans. We can justify the font downloads there since the audience is so much smaller. Fun fact, when I worked at Adobe we gave those typeface designers lots of feedback that we'd like to discern between I and l so that's why their lowercase ls have curves. I also use Source Sans in a side project. – Aaron Shekey 22 hours ago
  • 2
    I would prefer Source Sans/Serif/Code Pro series of fonts. And I’m sure other people would have their own font preferences too, @ErkinAlpGüney – Martin Bean 20 hours ago

12 Answers 12

28

Multi-disciplinary designer chiming in here.

However, Arial doesn’t ship with Linux distros or Android devices. We’re currently only achieving consistency between macOS, iOS, and Windows, leaving 2 platforms to choose their system font.

Why are you not loading the Arial webfont?

We’d rather have the consistency be shifted to the device itself—when viewing Stack Overflow on iOS, it’ll feel that much more native in San Francisco. Same with Android, which is already being displayed in Roboto.

What is the advantage of feeling more native? Is Stack Exchange not its own brand with its own identity?

We should also note that prior to these changes, our monospace font stack varied wildly. Now you'll have better consistency between sans and monospace, since we'll do our best to choose the right pairings.

You can still select the right pairings going forward and have it be consistent across each platform.

If consistency were the absolute goal, we’d ship our own custom font. I would love to be able to truly express our brand through a typeface, but that means users would have to download custom fonts and wait for them to display.

You can achieve consistency without making your own custom font. There are plenty of websites that download off-the-shelf well-designed fonts. Text is rendered and then styled, so even if there was a delay in loading the generally small (~100kb) font file, the text would be displayed in the default browser font temporarily—making it still readable as it doesn't require any "waiting" for the text itself to display. Regardless, the font file is downloaded once on first visit.


As a designer, this move baffles me. I use a Windows computer, an Android phone, and an iPad tablet and each one will look different from each other, but look native to the device they're on? I fail to see the real reason for this move. What is the advantage of looking native to a device? Has any other company done this (purposefully) and if so, what was the outcome? Do your designers on staff agree with this decision?

I'd love to hear any and all comments or thoughts.

New contributor
Davbog is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
7
  • 1
    Not a designer, but the move might be influenced as a replacement of native (web) app on mobile (since the official SO and SE mobile apps have been "sunset"), like how Flutter decides the font for different OS. – Meta Andrew T. yesterday
  • 4
    [Also not a designer] Personally, if it makes things more legible I'm all for it. I remember when Ask Different used to have its own, very clean font; then a few years ago everything went to the same fuzzy font that Super User had been using. I'd like 'clean' back & if that's San Fransisco, then that will suit me just fine. I honestly don't care how it looks on Windows [nor do I imagine Windows users will care how it looks on Mac] Responsive design means it's going to look different on every screen anyway. – Tetsujin yesterday
  • 3
    Currently there is a tension between achieving a consistent look for branding purposes and making the site look good. The version of Arial which Microsoft licensed for use as a web font is from 1996. It only has about 500 characters. The typeface itself is from 1982 when we used fuzzy CRT monitors. If they used that, then type quality would go down on millions of devices and scattered bits of text would be displayed in visually incompatible fallback fonts. – David42 yesterday
  • 11
    A fellow designer! 👋 We have opted to not load webfonts at our scale. Stack Overflow, despite being one of the top 50 visited websites, is fast and we'd like to keep it that way. Everything's a budget, right? We download CSS, JavaScript, and maybe eventually, fonts. We'd have to delete a lot of legacy CSS before we have the budget for fonts. For now, this allows us to modernize our typefaces. – Aaron Shekey yesterday
  • 5
    Hard to address each of your questions, but lots of your questions are addressed in my original post. Our designers agree with this decision. Many websites, including what I consider our peers take this system typeface approach, GitHub being the closest audience we have. – Aaron Shekey yesterday
  • 1
    "Our designers agree with this decision" says the Op. This is a bad reason for the points mentioned by @Davbog - I feel like it is something only you want. – JonH 14 hours ago
  • 1
    Basically, they're following the train of others companies doing the same. On a personnal note, it's true that if each site I would visit had a distinct font, it might hurt my eyes to constantly switch from one font to another. – Walfrat 9 hours ago
26

As you consider the font stack, please do consider revisiting this very popular request: "Can we at least select our fonts?". Yes, it is marked , but the "New plan is the old plan, mostly" and these fonts are still inappropriate for a significant number of sites.

7
  • 11
    Thanks for posting this. As someone who is legally blind, but has some vision, Segoe UI has been the bane of my life since upgrading to Windows 10. I've sunk hours into doing whatever I can to get away from it because of how dreadful a font it is. I agree with @Davbog's answer. I don't care about whether something will "feel that much more native", I want to be able to read the content without straining my eyes doing so. – John H yesterday
  • 6
    @JohnH I recently, to my delight, discovered Atkinson Hyperlegible. So far, it and Plex Sans are the only sans-serif fonts (that I've found) featuring both slab-serif uppercase Ɪ and lowercase ɭ with a tail, allowing immediate stand-alone recognition without requiring the other character adjacent to be sure what | means. – Adám 21 hours ago
  • 2
    Adam, that's really thoughtful of you to link those fonts - I appreciate that. I'll give them both a try and see how I get on. – John H 21 hours ago
  • 2
    Note that what they status-completed seems to be: allow each site to customize its fonts. What you seem to want if I'm reading the request correctly is to allow each user to customize the fonts. It might be worth editing that into this suggestion so that it is more obvious if Stack employees read it. Or if I'm misunderstanding, perhaps more explanation would help (it doesn't matter if I understand, but you don't want Stack employees to misunderstand). – mdfst13 6 hours ago
  • @mdfst13 I think it is quite clear that the post speaks about sites wanting specific fonts. E.g. it says "Sites that use Unicode characters extensively, like Japanese.SE, will want" and "sites that need an alternate font". – Adám 5 hours ago
  • 2
    Then I think that is why they are saying that it is completed. They can set site-specific fonts. If you want a font change for a specific site, you might be better off posting in that site's meta. Because first you want to get community consensus on the site and then ask for a change to that specific site from Stack. Getting community consensus on the common Meta doesn't ensure that the font will be correct for the specific site. So customizations on a per-site basis should be discussed in each site's meta. – mdfst13 5 hours ago
  • 1
    @mdfst13 Except such requests will be refused: "Themes can specify what elements use serif, sans-serif, or monospace fonts." i.e. not which fonts at all. – Adám 4 hours ago
21

Rapid observations

Interesting change. Confusing title. Strange timing.


Interesting change

This looks to be a network-wide change, except when it isn't. Any site not already customized will switch to the new version, while customized sites get to keep what they have (or don't get the latest and greatest change). So long as the results are still readable, or no less readable than the current settings, it's fine. Telling the difference between uppercase /ˈaɪ/, lowercase /ˈɛl/ and Arabic numeral one can be difficult at a glance. Similar difficulties exists between uppercase /ˈoʊ/ and Arabic numeral zero. With luck the font served will resolve the issue.

Confusing title

The term "system fonts" made me hopeful, at first. Thinking to myself that now whatever fonts I've set my system to use for serif, sans-serif and mono space would be used in my browser as well. Well, the title was promising in that regard. Rather, if the change works as intended, the site will use a font which my OS supposedly ships as the default "system" font. Well, for the "top five" anyway: Android, ChromeOS, Windows, MacOS, and iOS.

Strange timing

Of all the things needing developer and designer attention on the network, this seems the least often mention, or requested, change. I've no idea how many sites have been out of Beta, or for how long, waiting on a customised theme, even a tiny bit to make them "unique" within the network. As mentioned in a comment, dark mode was introduced to SO over a year ago. Applying dark mode to the majority of the sites would seem to be less work than selecting and testing a new font stack system wide.


What I think

(All in random order)

The "Why" section references a GitHub blog as covering the reasons for switching. The same blog entry explains why they dropped the Ubuntu font, yet it appears to be included in the font stack here. If GitHub had issues with that font using their modest, by comparison, site styling, what problems can be expected within this network?

The table of font to OS association contributed to my initial thought that the "system font" would be applied to the site. Using a custom font stack, which is supposed to have the site's fonts match the device's system font to create a seamless user experience only works until the user has selected a different font for their device. Worse, if the user has selected a different font they may be upset that SE refuses to acknowledge that choice.

Even if it's not a custom font for SE, though that was stated as a possibility in the future, using a downloadable font, with decent fallback options in the font stack seems like a better option for creating a "brand" feel rather than trying to create an "app" feel which is so demonstrably fragile. The wait for it to download, even on a mobile device should be minimal, and is likely cached by the device for future page loads as well.

Also interesting is the desire to modernize the style, but only for the sans-serif and mono space fonts. If the "old is bad and new is good" is to be part of the rationale, why leave the old serif fonts untouched? Times and Times New Roman (1931) are older than Arial (1982), and Georgia (1993) is not much newer.

As mentioned earlier, the differences between uppercase /ˈaɪ/, lowercase /ˈɛl/ and Arabic numeral one can be difficult at a glance, as can the difference uppercase /ˈoʊ/ and Arabic numeral zero. Finding a set of fonts, especially in the mono space group, would probably do more for the users than aiming to update the fonts just because the current set is "old".

I frequently see references to the design system (Stacks), and how much easier it makes design change implementations. In this case because the font stacks can be stored as CSS variables. Somehow, whenever other, user desired, design changes are mentioned, the typical reply is akin to the idea that it's too hard, or take too much time, or involved too many resources. I've yet to decide if the Stacks took is helpful or not, in actual application by the team.


I'm not opposed to a fresh new look. It's even a good thing to keep a fresh feel to the site. I also do not personally care which fonts are used, or even if serif or sans-serif is the norm. The timing, while short, isn't a problem, nor would it be if there had been no notice at all. Odds are that less than half the users will even notice the change. I am a bit surprised that this change was not significant in requests or complaints on meta yet seems to have been fully developed without feedback from users.

It's my hope that the reading won't be any more difficult than it is.

8
  • 2
    "seems to have been fully developed without feedback from users" - unfortunately, that's how things are done these days. I'm saying this considering the last design changes (this and this, just to mention 2 examples) - and regardless of all the negative feedback and requests to revert them (here and here), SE kept those changes, ignoring the community. That's their current modus operandi, unfortunately our opinion doesn't make any difference to them. – hkotsubo yesterday
  • 1
    The font used will actually be system-ui. This should be whatever you set as your system font, if the OS allows that. So exactly what you wanted, if I understood you correctly. The new CSS does not hard-code font names. – Konrad Rudolph yesterday
  • 2
    Oh I wish it were easier to address things via comments. There exists the concept of quick wins on decades-old software, and this is one of them. Making themes and ensuring they're all dark-mode aware is not a quick win. It'd take me about 10 months to do, exclusively, and that assumes those changes have the largest impact. – Aaron Shekey 23 hours ago
  • @KonradRudolph If the design does use system-ui the results will be nearly identical to what they don't want, Helvetica and Arial defaults. My current desktop uses Noto Sans and my browser is set for Source Sans Pro. The page you directly linked to explaing system-ui still selects Arial. i.stack.imgur.com/GElc0.png – Chindraba 22 hours ago
  • 1
    @Chindraba No, you’re misunderstanding computed style in the screenshot. The arial value is being overridden by the cascading style value system-ui. And the selected text in your screenshot is very clearly not using Arial. – Konrad Rudolph 18 hours ago
  • 4
    @AaronShekey "Modern" is not automatically a win, quick or otherwise. The only thing I see here even approaching an actual reason is some vague mention of high resolution devices and ill-defined notions of "readability." I don't see any specification of what problem you're actually solving, just common, vague platitudes that tend to create more trouble instead of solving problems. But your comment is a cop out, anyway. You have a whole question post to explain the issues you only reference here and chose not to. – jpmc26 16 hours ago
  • @KonradRudolph I stand corrected, it is picking up on my browser's setting and using that. The "system" is set to Noto Sans, and the browser is Source Sans Pro, which is the final font used to display that segment. The on-device consistency is still lost, and the user is given more control. +1 for the user wishes, -1 for designer wishes. – Chindraba 15 hours ago
  • 3
    Moving forward without feedback from users seems to be part of the Stack DNA. – Mark Ransom 14 hours ago
14

My 2¢:

  • Arial is a lame Helvetica knockoff and should not have been used to begin with IMHO. But just because you're moving away from it, doesn't mean you need to switch to a weird font selection scheme.

  • Like @Chindraba says - opting for system fonts is just fine. So - don't set the specific font family; just use the fallback sans-serif always. It's not like you were using some exquisite custom font so far. SE is about the text, not the styling - winter bash knitting aside.

  • You wrote you want to achieve consistency. Well, forcing those font family choices does not constitute consistency. Going for sans-serif does: The fonts won'y be identical, but they will be chosen consistently (and in accordance with the user's preferences).

  • Why is Ubuntu singled out? There are dozens of Linux distros, you could pick-and-choose fonts for them as well, right? ... naah, doesn't make sense. But then, it doesn't make sense for Ubuntu, nor for Windows, where older versions use Tahoma rather than Segoe (for their UI); and older versions still use MS Sans Serif.

Oh, and now that we're talking: How about that unnecessary 1.5x spacing?

7
  • “opting for system fonts is just fine. So - don't set the specific font family” — That’s in fact exactly what they’re doing. The Staging stackoverflow.design use font-family: system-ui. – Konrad Rudolph yesterday
  • 2
    @KonradRudolph: Well... that's not what the OP says. If what you said is verified I'll drop most of my post. – einpoklum yesterday
  • Setting sans-serif doesn't choose the system font though. On macOS, sans-serif maps to Helvetica. On Windows, it's Arial, a lame Helvetica knockoff we want to avoid. As for Ubuntu, we chose to specify that particular linux distro because it's our most popular. Is there another distro we should respect? – Aaron Shekey 23 hours ago
  • 2
    @AaronShekey Part of my original comment which didn't make it to my answer was about Ubutu vs. Linux. Is there another distro we should respect? Not so much another "one" you should respect so much as none you should neglect. Instead of "Ubuntu" how about "Linux"? Technically Android and ChromeOS are also Linux, and the most popular of all distros. Desktop-wise Mint, MX Linux, Manjaro and Debian rank higher in most cases. Not sure how SE determines their most popular. Possibly from User-Agent headers or developer survey answers. – Chindraba 23 hours ago
  • 3
    Android and Chrome OS will render as Roboto. Ubuntu will render in Ubuntu. I considered adding "Cantarell" for GNOME. Seems some folks are also using OxygenOS so we could add "Oxygen" there. I considered "Fira Sans" for FirefoxOS but it seems to be canceled? – Aaron Shekey 22 hours ago
  • @AaronShekey: sans-serif does choose the system font in the sense that the site visitor's system chooses a font to render no-specific-family sans-serif text. And the user, or a desktop environment theme, override this with the font family they like. – einpoklum 21 hours ago
  • 2
    @einpoklum Browser standard font ≠ system font. It so happens that what browsers use as default standard fonts are not the system UI fonts and, on Windows in particular, the default is sub-par (= Arial). And on macOS the user can’t choose the system UI font as the browser standard font (without first manually installing the font files separately). – Konrad Rudolph 18 hours ago
8

Is this change fully verified if it applies to sites that use non-English languages?

Our site (So.ja) took seven years until the design bug due to font specification was fixed.

1
  • 3
    We were discussing this internally, and it looks like, yes, these font stacks work well in Japanese. If the community disagrees and we need to bail, we can always specify the existing Arial on a per-community basis. In theory, moving to system fonts should give us more international characters, not less. – Aaron Shekey yesterday
5

On Android Firefox it seems like it will permit more text on screen, compare before, after, and overlaid; though it will also change the number of characters on a line, and reopen (or aggravate) the bug reports about long names / tags, and overflowing columnar text.

4
  • 3
    Where are you getting your after screenshot from? We haven't shipped these changes yet. Regardless, the font shouldn't change at all on Android, since we're already rendering it today in Roboto since Android doesn't have Arial. 🤔 I've verified using the Stacks documentation site that the current production text matches the proposed font stack exactly. You can compare production to staging. – Aaron Shekey 2 days ago
  • @AaronShekey, Comparing production and staging shows those fonts are identical; the only difference in the superimposed images is the browser's URL field. --- My example was produced by using my phone's UI to access the Accessibility Settings and force the font change to be applied; that's no different from a different browser where you would change the fonts, nor the result that would be expected, and the applicability of those other reports. – Rob 2 days ago
  • A perhaps simpler explanation is that fonts have different names because they are different, excluding someone who has created a font by copying and renaming. While the anatomy may be consistent the vertical and horizontal proportion usually differs when rendered at the same size; and decimal sizes still don't align exactly depending on the character composition of each line. – Rob 2 days ago
  • Here's a very small sampling of some of the complaints, which are supportive of my answer here, that resulted when we changed the fonts: meta.stackexchange.com/q/316797/282094 meta.stackexchange.com/q/353525/282094 meta.stackexchange.com/a/316196/282094 meta.stackexchange.com/q/311033/282094 meta.stackexchange.com/q/317237/282094 – Rob 2 days ago
1

Can you consider adding "Segoe UI Variable Text" before "Segoe UI" in the font stack for Windows?

Microsoft will gradually update Windows UI with this new font in the future: Announcing Windows 10 Insider Preview Build 21376 | Windows Insider Blog

We are introducing Segoe UI Variable which includes an optical axis so that font outlines can scale seamlessly from small to larger display sizes. Segoe UI Variable is a refreshed take on the classic Segoe, now with improved legibility at small sizes, and much improved outlines at display sizes.

Historically, fonts for printing small text were designed differently than fonts designed for large display text. Segoe UI was originally designed to work at 9pt, which makes it a great font for that size, but limits expression at large sizes and lacks legibility at even smaller sizes. Segoe UI Variable solves this by using a new version of Segoe that uses variable font technology to dynamically offer great legibility at very small sizes, and style at large sizes.

Segoe UI:

Segoe UI Variable:

4
  • Addressing your edit: AFAICT, the font name is just "Segoe UI Variable". It contains neither the word "Text" nor "Display". – 41686d6564 3 hours ago
  • 1
    @41686d6564 there are multiple fonts in "Segoe UI Variable" family that's why I wrote the full name, but, yeah, maybe it's not relevant. – Swisstone 3 hours ago
  • Ah, I see...... – 41686d6564 3 hours ago
  • 1
    I'll look into this, thanks for bringing it up @Swisstone. – Aaron Shekey 1 hour ago
0

Do we have to force refresh/flush cache Stack Overflow websites for it to re-cache the new fonts or not?

New contributor
SirStopIt is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
2
  • Our cache on the CSS side isn't too aggressive, so I don't think you'll need to do anything fancy to see the changes when they're live. – Aaron Shekey 1 hour ago
  • Ok, this is good to know then. – SirStopIt 1 hour ago
0

I currently use SE on multiple devices, with multiple OS' (Windows, Mac OS, Android). Personally I would prefer a uniform site on all these devices, also as not to break my muscle memory (seeing that text will change in length buttons will inadvertently shift in the layout).

I know that you decided different, which is a great option for users using a single device. But at the same time SE also has the history of being highly customizable using one's profile. It would be great to have such a setting for the font as well. That way we can override the system font with a font of our picking. This would also be a great feature for those that have less then perfect eyesight and want to use a more accesible font.

2
  • It may be worth investigating how to override the font settings in your browser, so that they will apply across all sites, not just Stack Exchange. I know Mozilla lets you do this in General Preferences -> Language and Appearance (click the advanced button to disallow sites to override your fonts and set a minimum font size) – ColleenV 52 mins ago
  • Whilst certainlyna solution fornthe more tech-savvy users I think a profile option would be far more user friendly. But this is indeed very much a "nice-to-have". @ColleenV – Luuklag 16 mins ago
-1

You may want to consider a font from the candidates for new default fonts for Windows expected in 2022. And if you consider that, you may want to wait until Microsoft makes their final choice, or stick with Segoe UI until then, and then switch. Just a thought.

I do recognize all Windows users aren't Windows 10 users. Perhaps Segoe UI for Windows <10 and one of the new ones for Windows 10.

8
  • 2
    The article isn't talking about replacing Segoe UI, the font in user interfaces, but Calibri, the font used in Office. Don't see a need to change here. – Sonic the Anonymous Hedgehog yesterday
  • I'm not following. I don't see Calibri mentioned anywhere. My thoughts are if you are going for a Windows system font for browsers on WIndows, at some point, they may want to look at those (around 2022). – Kit yesterday
  • 1
    To quote from the article (emphasis added): Microsoft has commissioned five new fonts as potential replacements for Calibri. – Sonic the Anonymous Hedgehog yesterday
  • 1
    @SonictheAnonymousHedgehog hmm that article says "Microsoft has commissioned five new fonts, one of which will replace Calibri as the default font to be used in Windows, Office and more" and "Calibri went on to be Microsoft's default font everywhere", indicating it's not just for office. – Cave Johnson yesterday
  • 2
    Also, what about users who choose to run older builds of Windows 10, such as the LTSC branch or simply an older release build? I'm still running 1909 on my laptop (and have the Education edition so it's still supported). – Sonic the Anonymous Hedgehog yesterday
  • @SonictheAnonymousHedgehog Sorry - I misread the word "article" as meaning the OP here at meta. – Kit yesterday
  • 1
    I'm using Windows 7. – Andreas Rejbrand yesterday
  • 1
    Arn't system fonts set... system wide? So if windows 10 v21Hx sets the new font as a default, everything will switch with it. And while unsupported, other OSes may have their own font choices, not that explicit haiku support is a given – Journeyman Geek yesterday
-1

Please bring back the old line-height 1.3 setting

I find new fonts (I'm on Windows, so Segoe UI) look even worse with the current settings. It's more comfortable to read with thinner fonts at more compact line heights.

Screenshot for current (1.5):

LH 1.5

Screenshot for line-height: 1.3

LH 1.3

2
  • 3
    Just to offer an opposing point of view, I find your 1.5x line-height screenshot more readable. 1.3x looks cramped. And to put this statement into context: I am hawkish about not wasting vertical space for code readability, and I consciously broke my University’s rule when submitting my PhD thesis because I refused to adhere to their overly large line spacing requirements. So I’m certainly not biased towards large line spacing. – Konrad Rudolph 7 hours ago
  • (And if we’re bikeshedding, I’d prefer a slightly tighter spacing than 1.5 with the specific typeface and line length in the screenshots. But I’d also prefer properly typeset, justified paragraphs and no modern browser can do this properly so it’s not happening.) – Konrad Rudolph 7 hours ago
-4

I, for one, have been blocking remote fonts on all sites by default (including StackExchange) for years -- using UBlock Origin.

Seems like I'm using "system fonts" already...

2
  • 1
    “Seems like I'm using "system fonts" already...” — You weren’t, that’s the whole point: system UI font ≠ browser standard font. – Konrad Rudolph 18 hours ago
  • 7
    If I'm not mistaken, uBlock isn't blocking any of our current fonts because they aren't remote, nor will they block future fonts. @KonradRudolph's right, your fonts may still change even with uBlock. – Aaron Shekey 18 hours ago

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .