Closed Bug 1641651 Opened 5 years ago Closed 5 years ago

MultiStage about:welcome should be using Metropolis font-family

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

RESOLVED INVALID
Iteration:
79.1 - June 1 - June 14
Tracking Status
firefox78 --- wontfix
firefox79 --- wontfix

People

(Reporter: pdahiya, Assigned: emcminn)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Using metropolis font-family will help maintain design consistency with the download pages on firefox.com

https://mozilla.design/firefox/typography/

Assignee: nobody → emcminn
Iteration: --- → 79.1 - June 1 - June 14
Priority: -- → P1

After some trying things and discussion, I'm thinking we should probably drop this bug. It was brought up to me this morning that a lot of our localized non-english pages don't use Metropolis anyway, because it doesn't include non-latin glyphs - so all those pages fall back to Helvetica. (Even weirder, it'll only fall back for glyphs that aren't present, so we'll have different fonts within words in some locales.)
On top of that, we may run in to build size issues once we bundle the fonts.

It seems like our best bet for consistency would be to use the next closest font (Helvetica) across all the about:welcome pages, so that we don't get mismatched glyphs with localization.

Aaron, do you think Helvetica would be the right choice of fallback here, or is there something else we could pick that's closer? (Bearing in mind that non-latin locales will fall back to Helvetica anyway.)

Flags: needinfo?(abenson)

Just so I understand, is the fallback font for non-latin locales or are we saying we'd use the fallback font everywhere?

The suggestion was to use the fallback font (Helvetica) for all the in-product (i.e. about:welcome) pages in all locales, since that will match the localized download pages.

In that case we should do what we do for other in-content pages and for menus and fall back to the system font. San Francisco for macOS and Segoe for Windows.

Flags: needinfo?(abenson)

FWIW - I hear that Fenix is shipping with fonts and there's no licensing issue here. Is there concern around file size?

Flags: needinfo?(emcminn)

(In reply to Aaron Benson from comment #8)

FWIW - I hear that Fenix is shipping with fonts and there's no licensing issue here. Is there concern around file size?

That was one of the big concerns, yeah. I'm not sure who would make decisions about how much is too much, though.

Flags: needinfo?(emcminn)

(In reply to Aaron Benson from comment #8)

FWIW - I hear that Fenix is shipping with fonts and there's no licensing issue here. Is there concern around file size?

Will do, thanks!

It looks like those font are what we have implemented by default, so we're good :)

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: