1611450 - Glitchy Font Rendering for "Josefin Sans"

Status: UNCONFIRMED

(Core :: Graphics: Text, defect, P3)

Description

[Martin]

Attachment: screenshots.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Visit https://glassjore.com/

Actual results:

Josefin Sans font renders improperly compared to different browsers and prior version of Firefox. The lettering is now narrow and in paragraphs, the font appears wiggly and/or garbled, bold is also seemingly not rendered properly.

This font has flagged issues with Firefox SVG rendering in past:
https://bugzilla.mozilla.org/show_bug.cgi?id=1544432

No files on the site have changed.

Expected results:

Josefin Sans font renders properly as in screenshots provided with other browsers and prior version of Firefox.

Comment 1

[Gingerbread Man]

Attachment: Screenshot - Firefox 72.0.2 on Windows.jpg

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
20200117190643

I don't see those issues. The only difference I notice is that in Vivaldi the lines are slightly thicker and brighter. I don't know if something that subtle would even be considered a bug.

Comment 2

[Gingerbread Man]

Attachment: Screenshot - Vivaldi 2.10.1745.27 on Windows.jpg

Comment 3

[Martin]

Your screenshot of Firefox 72.0.2 is different from mine. Please check the screenshots I sent above, in detail. Can you replicate that?

And further, please compare the other pages. For example, this one: https://bit.ly/2RpzbY7 How does that render for you? The glitch there is making the font render horrible in paragraphs. And bold is missing.

I know it's a small detail, but has something in Firefox has changed and we're having problems again? 72.0.1 works fine for me.

Comment 4

[Martin]

https://bug1611450.bmoattachments.org/attachment.cgi?id=9122906

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:lsalzman, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

[Lee Salzman [:lsalzman]]

If you go to "about:support", in the "Graphics" section under "Compositing" does it say you are using WebRender? If so, can you try disabling WebRender and see if the problem goes away?

Comment 7

[Daniel Holbert [:dholbert]]

For what it's worth, I can't reproduce the issues reported here either (in Nightly 75 & current release, which is now 73). I tested on Win10 as well as Linux (Ubuntu 19.10), and I tried it with webrender off (by default) as well as manually opted-in, when I tested version 73.

If so, can you try disabling WebRender and see if the problem goes away?

(BTW -- to do this, go to about:config and set the preference gfx.webrender.force-disabled to true.)

Comment 8

[Martin]

Hi there,

Thank you for your efforts.

Yes, according to about:support, WebRender was being used so I disabled and restarted Firefox, it now says "Direct3D 11 (Advanced Layers)" and the font rendering as reported still exists. :(

I've also accepted the recent Firefox update to 73.0, and the issue still exists for me, both with WebRender enabled or disabled.

Comment 9

[Daniel Holbert [:dholbert]]

Thanks for trying that & reporting back.

Given that we haven't been able to reproduce yet, would you mind testing a brand new Firefox user-profile, just to rule out the possibility that some setting got mistakenly toggled in your normal Firefox profile?

(To do that: go to about:profiles, click "Create a New Profile" at the top, click through the dialog, and then go to the bottom of that about:profiles page to see the entry for your new profile, and click "Launch Profile in New Browser".)

Comment 10

[Jonathan Kew [:jfkthame]]

From the screenshots, I thought this looks like it could be related to particular font rendering settings (ClearType/Font Smoothing options), but I've tried adjusting those in various ways on my Windows machine and wasn't able to reproduce the bad appearance here.

Martin, could you please attach your full about:support, in case there's anything in there that might give a clue as to why you're seeing a different result?

Comment 11

[Martin]

Sure thing. I just tried creating a new profile called "testing" but the issue unfortunately still persists for me...

Here's the contents of about:support: https://pastebin.com/hAdyS8Vn

Comment 12

[Gingerbread Man]

Attachment: Reporter's about:support

Comment 13

[Martin]

Hmmm. I've since noticed that this machine is using Windows 10 LTSC. Perhaps that's a contributing factor.

screenshot