rsalvaterra@ Thanks for the issue.

This issue seems to be similar to  issue 857511 . Hence merging this issue to  issue 857511 .
Please feel free to undupe if it is not the case.

Thanks..

#3: Indeed, hence my comment on  issue 857511 . I only opened this one because I was told otherwise by a member of the Chromium team.

rsalvaterra@ Thanks for the update.

As per comment #4, unduping the issue and adding the 'Needs-Bisect' label for further triaging.

Tested this issue on Ubuntu 17.10 on the reported version 69.0.3486.0 and the latest Stable 67.0.3396.99 by following the below steps.

1. Launched Chrome on the Dev 69.0.3486.0 and Stable 67.0.3396.99 and navigated to https://en.wikipedia.org/wiki/Main_Page.
2. Compared the fonts on both Stable and Dev and could not observe any difference in fonts, except for the text appearing a little bold on the Chrome Dev version.
Attached are the screen shots for reference.

Request you to check and confirm if anything is missed from our end in triging the issue.

Thanks..

Deleted: 862434-M67.png 884 KB

	862434-M67.png 884 KB View Download

Deleted: 862434-M69.png 778 KB

	862434-M69.png 778 KB View Download

Hi, Susan,


You are testing with a much higher resolution, so the differences aren't so apparent, especially regarding hinting. I suggest you try at 1024x768. Nevertheless, you can clearly see the misalignment on the text baseline and midlines. Additionally, the fonts are rendered with grayscale antialiasing, not LCD antialiasing.
I'm attaching two zoomed details of the images you attached in #5, where you can clearly see the problem I describe.


Thanks,

Rui

Deleted: M67.png 40.3 KB

	M67.png 40.3 KB View Download

Deleted: M69.png 40.1 KB

	M69.png 40.1 KB View Download

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

Able to reproduce this issue on Ubuntu 17.10 on the reported version 69.0.3486.0 and the latest Dev version 69.0.3488.0 as per comment #6.
Issue is not observed on Windows and Mac OS.

Bisect Information:
===================
Good Build: 69.0.3483.0 
Bad Build : 69.0.3484.0

On executing the per-revision bisect script, RuntimeError is coming up. Hence below is the manual Changelog URL from omahaproxy.

https://chromium.googlesource.com/chromium/src/+log/69.0.3483.0..69.0.3484.0?pretty=fuller&n=10000

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1127028

drott@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding 'ReleaseBlock-Beta', as this is regressed in M-69. Please feel free to remove if this is not applicable.

Thanks

rsalvaterra@, thanks for the separate report. Now with a clear description and reproduction, it does seem to be a duplicate to  issue 857511 , but it was important to clarify the error you were seeing. We now see clearer as to what the issue with FontConfig is in this case. It seems all rendering settings are affected, antialiasing as well as hinting.

I'll assign this to thomasanderson@, as he started proposing a FontConfig fix in upstream. I'd leave it to him to decide whether this is a duplicate or not. 

On second thought, this is slightly different from  issue 857511 . 857511 has completely different fonts matched, while here, different rendering settings are applied. 

rsalvaterra@, what Linux OS is this on and did you do any customizations to your FontConfig configuration?

Okay, I see it's Ubuntu 18.04 MATE, with excerpts from your FontConfig settings attached above.

In all screenshot, there is a regression in that the monospace font is replaced with a proportional font, this seems to be  issue 857511 .

The Wikipedia screenshots however also demonstrate issues with wrong and inconsistent hinting. I'll investigate whether that can be attributed to https://chromium-review.googlesource.com/1127028

rsalvaterra, can you right click on one of the bullet points of the "In the news" section of wikipedia, in stable and dev version of Chrome, then click "Inspect", go to the computed styles tab, scroll down and list the fonts that are used?

(Compare this screenshot from Mac just for instructions.)

susan.boorgula@ - can you post screenshots from your reproduction and also explain which fonts you see used?

Thanks.

I've tried to reproduce with Ubuntu's standard Fontconfig configuration, as well as a modified one set to lcddefault filtering and hintnone hintstyle, but I do not get the same issue. The sans-serif font used on my system, with a clean profile, is Arial (as it is installed), but I think the font in your screenshots is a different font.

Deleted: used_font.png 800 KB

	used_font.png 800 KB View Download

Hi, drott,

At the moment I'm at work, so I only have ssh access to my machines. In any case, the font packages I have installed are:

fonts-liberation
fonts-mathjax
fonts-noto
fonts-noto-cjk
fonts-noto-color-emoji
fonts-noto-hinted
fonts-noto-mono
fonts-noto-unhinted
fonts-ubuntu
ttf-bitstream-vera

I have no manually installed fonts besides these. Yes, my systems are somewhat customised. In addition to the fontconfig settings showed previously (which I changed to "assign" instead of "append"), I also created a rule to disable embedded bitmaps (boy, do I loathe them) in fonts, but it doesn't apply here.

rui@presler:/etc/fonts/conf.d$ cat 20-no-embedded-bitmaps.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <match target="font">
    <edit name="embeddedbitmap" mode="assign">
      <bool>false</bool>
    </edit>
  </match>
</fontconfig>

Still, everything was working fine until a few dev releases ago. Let me know if there's something else you need.

Thanks for providing more info, though I think this issue shares the same cause as the original, so I'm merging them.

thomasanderson@, were you able to confirm this reproduction as fixed as well? rsalvaterra@, would you retest this once the Linux dev version reaches 69.0.3494.0? 

Sure, will do!

> thomasanderson@, were you able to confirm this reproduction as fixed as well?

Yes.  I was testing with Ubuntu 18.04 on wikipedia.org.  After the patch restores the Chrome 67 font settings.

Updated moments ago to Chrome dev 69.0.3497.12 and I confirm the issue is fixed on my side. Thanks to everyone involved!

Thanks for retesting.