: Why doesn't Segoe UI font work in Google Chrome on Metro Bootstrap? When viewing the Metro bootstrap in Firefox, the font looks as it should, while in Chrome it defaults to what I assume is

@Deb1703797

Whilst I am not familiar with the Windows fonts in question, this issue may be due to the way different browsers look up font names. WebKit looks up font-family names first by checking the PostScript name of the font for a match, so if you have, for example font-family: "UniverseLT330", "UniversLT", "Univers", san-serif; then WebKit will match UniversLT330 if available, despite that representing a face not a family. Mozilla will only look for family name matches, and therefore match "Univers" if available, and sans-serif otherwise. Could it be that you have a different font name before Segoe UI that Chrome is picking up and Firefox is missing? Without seeing the CSS we're kinda stabbing in the dark here though.

Vote Up Vote Down

@Bryan171

No, Segoe UI does not come bundled with Firefox.

Segoe UI is the default for interface elements for Windows starting with Windows Vista and Microsoft Office 2007. So, Segoe UI and other Segoe variants can be obtained by installing Office 2007 or later, or Windows Vista or later.

More information can be found here:

www.microsoft.com/typography/fonts/family.aspx?FID=331 en.wikipedia.org/wiki/Segoe#Segoe_UI

Therefore, machines running Windows XP, or non-windows OSes might not have this font installed. Looking at the Metro bootstrap CSS it should fall back to "Helvetica Neue". Which is a font that is installed on most Mac's.

If none of Segoe UI variants or Helvetia Neue it falls back to the default Sans-serif font in your browser. Ironically, this seems to be Segoe UI (at least, on my machine).

Since this too doesn't render the page in Segoe, i assume that the system where you are running chrome on, doesn't contain the Segoe fonts.

As far as I am aware, Word for Mac does not install the Segoe fonts.

Vote Up Vote Down