Open Bug 1788721 Opened 2 years ago Updated 1 year ago

Firefox on Android selects Roboto as serif font even for weight:100, while Chrome avoids it and selects Noto Sans

Categories

(Core :: Graphics: Text, defect)

defect

Tracking

()

Webcompat Priority P2

People

(Reporter: twisniewski, Unassigned, NeedInfo)

References

()

Details

As diagnosed at webcompat.com, the page in question tells Firefox on Android to render paragraph text with this CSS:

font-family: serif;
font-weight: 100;

Firefox selects Roboto, which appears much thinner than what Chrome presents, and is an inferior choice for readability. In fact, Chrome will select Noto Sans instead even if Roboto is added to the font-family style:

font-family:Roboto,serif;
font-weight:100;

It might be worth it for Firefox to follow suit and avoid Roboto for thin font-weights, for webcompat's sake as well as text legibility.

This is also affecting ThePointsGuy.com. Chrome is picking Noto despite the site requesting Roboto:

font-family: Roboto,sans-serif;
font-weight: 400;
Webcompat Priority: --- → P2
Severity: -- → S4
Flags: needinfo?(jfkthame)

Interesting. But comment #0 is incorrect. The following font-family setting doesn't apply serif on GeckoView. Our font config has "Noto Serif" entry.

.com-paragraph {
 font-family:Georgia,"serif";
 font-weight:100;
 margin-bottom:2rem
}

When I change to the following in devtools, it works expected.

 font-family:Georgia,serif;

Since quoted value, we expect that this is real font name, but system doesn't have real font name "serif"...

I guess that Chrome uses Skia, so it will use /etc/fonts.xml entry as alias.

    <family name="serif">
        <font weight="400" style="normal">NotoSerif-Regular.ttf</font>
        <font weight="700" style="normal">NotoSerif-Bold.ttf</font>
        <font weight="400" style="italic">NotoSerif-Italic.ttf</font>
        <font weight="700" style="italic">NotoSerif-BoldItalic.ttf</font>
    </family>
You need to log in before you can comment on or make changes to this bug.