New issue
Advanced search Search tips

Issue 865421 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 857511
Owner: ----
Closed: Jul 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Texts are rendered with incorrect font when the "standard font" is not set

Reported by x...@opera.com, Jul 19

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3472.3 Safari/537.36 OPR/56.0.3018.0 (Edition developer)

Example URL:
http://www.columbia.edu/~fdc/sample.html

Steps to reproduce the problem:
1. Make sure no custom font is configured
2. Open a web page that does not contain any css

What is the expected behavior?
Use a serif font (Liberation Serif was the default standard font in stable Chrome) to render the text

What went wrong?
Chromium uses FreeMono on Ubuntu.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes 67.0.3396.99

Does this work in other browsers? Yes

Chrome version: 69.0.3493.3  Channel: stable
OS Version: Ubuntu 18.04
Flash Version: 

When no custom font is configured in setting, the standard font, serif font and sans-serif font are all marked as "custom". Only fixed-width font has a value (Monospace).

This is the default setting when I installed Chromium. And any sites without CSS will be rendered with FreeMono.

Also, if only a missing font is set in the CSS (ex. font-family: "Arial"), it will also be rendered with FreeMono instand of a sans-serif font.
 
Labels: Needs-Triage-M69 Needs-Bisect
Components: -Blink Blink>Fonts
Cc: drott@chromium.org thomasanderson@chromium.org
Labels: Triaged-ET
Thanks for filing the issue!

This issue looks similar to the issue:  862434  & 857511, hence CC'ing: drott@chromium.org & thomasanderson@chromium.org,
drott@ & thomasanderson@: Could you please let us know if this issue is similar to Issue:  862434  and  857511  and provide your inputs on it.

Thanks!
I believe this is a duplicate, yes. Please retest with 69.0.3494.0? 
Labels: Needs-Feedback
As per comment# 4, this issue seems to be Duplicate of issue:  857511  and  862434 , for the issue:  857511  this fix is already landed and it has been verified.

@Reporter: Could you please try to test this issue on chrome version# 69.0.3494.0 and let us know if the issue still persists.

Thanks!

Hello, I only got 69.0.3493.3 from the dev channel today (https://www.google.com/chrome/browser/?platform=linux&extra=devchannel). I will let you know if it's fixed in 69.0.3494.0 as soon as it's available.

Regards
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 23

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 857511
Status: Duplicate (was: Unconfirmed)
Hello, I can confirm that the issue is fixed in 69.0.3497.12-1.

Thank you very much for your help and I am sorry for the delay.

Best regards,
Thanks for retesting.

Sign in to add a comment