Not just tabstrip (see e.g. bookmark bar).

This is clearly wrong and makes the browser hard to use.  Can we reproduce in house?  If so, we should get a bisect as quickly as possible.

Separately, it would be good to understand if this affects only certain WMs, GTK theme users, etc.  If this is broadly affecting lots of Linux users, this is very bad.

+CC estade & rpop, but I don't know who should own "firedrill" Linux-specific UI bugs.

I think oshima@ might have been the last to touch code that could cause this.

I'm not aware of any one who owns linux specific UI bugs.

One possibility is that if you have <1.0 font scale, chrome only scale down fonts but not UI because it's not supported. see  crbug.com/646254 

This could be the reason, at least for a couple of reports in pulse.

We can add an option or flag to control this behavior. I hate it, but I can't think of
any good solution that can satisfy both cases.

+thomasanderson spends a lot of time fixing Linux UI.

Feedback from an internal repro
24", 1920x1080, triple-head. Nothing changed about my displays or layout
since last chrome release.

Few users are also talking about experiencing this issue using 4K monitors in gfeedback. However, I was not able to repro this in VM with 1278 X 816 resolution. 

possibly related is  bug 685577 
However the reporter specifically mentions launching with "google-chrome with --high-dpi-support=1 --force-device-scale-factor=1."

CL sounds a bit suspicious?
https://chromium.googlesource.com/chromium/src/+/a98afff3156eb88b39f82cfae23d99bed436bb3c

That's what I referred in #3.

I'll look into it this weekends.

Have the same problem on my Dell UltraSharp U2913WM 29-Inch Ultra Widescreen display, 2560x1080 resolution (HDMI input).  The small UI fonts started on January 30th, 2017, immediately after I upgrading from Chromium 55.0.2883.87-0ubuntu0.16.04.1263 to Chromium 56.0.2924.76-0ubuntu0.16.04.1266

If I drag the Chromium window(s) to one of my 19-Inch Dell Displays, 1280x1024 resolution (VGA and/or DVI inputs) the UI fonts appear 'normal' sized.  Drag Chromium back to the 29-inch Ultrawide and the UI fonts become so small you can barely read them.

Zoom works normally on all displays - all resolutions - all inputs. It's just the UI fonts that don't scale properly.

After studying the (above) comments, I decided to downgrade (and pin) Chromium to ver Chromium 55.0.2883.87-0ubuntu0.16.04.1263

Everything is back to 'normal'. YaY !

I'll keep an eye on this discussion, and upgrade Chromium when the problem is fixed.

Happy hunting, and thanks !

 Issue 685577  has been merged into this issue.

Will send CL tomorrow.

Thanks for the updates.

Can anyone confirm whether we require any M56 stable refresh with this fix?

oshima@: Is it correct that this affects everyone using a high dpi monitor?

If that's the case, then this probably warrants a stable respin.

No, it's not everyone. The  issue #11  sounds weird though. AFAIK, linux chrome does not support dynamic scale change, so I'm not sure why. In any case, I'm moving this mode behind the flag so that this won't affect people who didn't opt-in.

I do not have a high DPI monitor

Can you check if you have set font scale settings <1.0? 

A friendly reminder that M57 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4ef351aa3467a587e03d8d19cdd9f280ab8fff4d

commit 4ef351aa3467a587e03d8d19cdd9f280ab8fff4d
Author: oshima <oshima@chromium.org>
Date: Wed Feb 08 23:05:19 2017

Don't allow font scale to be lower than 1.0

Many people who're using lower font scale do not expect this behavior, so
Let's revert this (logically) for now, and consider a solution for
low scale font if necessary.

BUG= 687770 , 646254 

Review-Url: https://codereview.chromium.org/2680393002
Cr-Commit-Position: refs/heads/master@{#449124}

[modify] https://crrev.com/4ef351aa3467a587e03d8d19cdd9f280ab8fff4d/chrome/browser/ui/libgtkui/gtk_ui.cc

OK, so I never intentionally set this font scale but it turns out it was set on 0.75. Setting it to 1 (and adjusting font styles accordingly to keep my system looking the same) fixed the issue and Chrome, and for the first time ever the fonts in Chrome are matching other windows. Hooray

#23  How did you change the setting?  (Asking on behalf of others who may be experiencing this issue)

Gnome Tweak Tool - it is possible to do it with Unity Tweak Tool too, but the scaling factor seemed to keep reverting to 0.75 with that

It's unfortunate IMO that what was recently fixed, is now being broken again. From comment #23, it appears the actual problem here is misconfiguration, which was now correctly exposed.

(Read bug for reference.)

https://bugs.chromium.org/p/chromium/issues/detail?id=629933#c8

Well, for me the issue is with only with Chrome. Opensuse Leap 42.1 and 42.2 + KDE. No gnome tweak tool in sight. And other GTK apps like Eclipse and Firefox are fine.

I have a question to those who are now affected by too small fonts: did you have this problem in versions of Chrome previously, particularly before M53? IMO the problem started with this (unnecessary?) commit.

https://chromium.googlesource.com/chromium/src/+/52c96f45954fb726585acd0bac295d801728b22e%5E%21/

If the answer is that it did work, then maybe Chrome could return to that state, and it'll work for everyone again.

> I have a question to those who are now affected by too small fonts: 
> did you have this problem in versions of Chrome previously, particularly 
> before M53? IMO the problem started with this (unnecessary?) commit.

55 OK, 56 not OK (like described in https://bugs.chromium.org/p/chromium/issues/detail?id=687080)

Yes, but I'd specifically need to know if Chrome before M53 worked. The reason is the following timeline of events.

53.0.2756.0: Font scale < 1.0 disallowed en-passant. This caused the fonts to be too large on devices that had explicitly configured lower font-scale.
Commit: https://chromium.googlesource.com/chromium/src/+/52c96f45954fb726585acd0bac295d801728b22e%5E%21/

56.0.2913.0: Font scale < 1.0 allowed again, which fixes the problem. (Not through a revert.) For some reason, it introduces the problem described in this bug.
Commit: https://chromium.googlesource.com/chromium/src/+/a98afff3156eb88b39f82cfae23d99bed436bb3c

And now this commit basically reverts the fix, and will re-introduce the first problem. Now if fonts were neither too small nor too large (respectively) pre-M53, then returning to that state can be the solution.

This issue seems to be impacting a lot more users than the problem in M53, approving for merge into M56.  A better long term solution can be used for future milestones.

Your change meets the bar and is auto-approved for M57. Please go ahead and merge the CL to branch 2987 manually. Please contact milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ff2efa3a0e3dd8e2ec8652da5cf08e9ac1e36153

commit ff2efa3a0e3dd8e2ec8652da5cf08e9ac1e36153
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Thu Feb 09 23:08:35 2017

Don't allow font scale to be lower than 1.0

Many people who're using lower font scale do not expect this behavior, so
Let's revert this (logically) for now, and consider a solution for
low scale font if necessary.

BUG= 687770 , 646254 

Review-Url: https://codereview.chromium.org/2680393002
Cr-Commit-Position: refs/heads/master@{#449124}
(cherry picked from commit 4ef351aa3467a587e03d8d19cdd9f280ab8fff4d)

Review-Url: https://codereview.chromium.org/2683653006 .
Cr-Commit-Position: refs/branch-heads/2924@{#907}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}

[modify] https://crrev.com/ff2efa3a0e3dd8e2ec8652da5cf08e9ac1e36153/chrome/browser/ui/libgtkui/gtk_ui.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8d5792c797a0850cefd3e1d6169caf2c390b97c9

commit 8d5792c797a0850cefd3e1d6169caf2c390b97c9
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Thu Feb 09 23:59:39 2017

Don't allow font scale to be lower than 1.0

Many people who're using lower font scale do not expect this behavior, so
Let's revert this (logically) for now, and consider a solution for
low scale font if necessary.

BUG= 687770 , 646254 

Review-Url: https://codereview.chromium.org/2680393002
Cr-Commit-Position: refs/heads/master@{#449124}
(cherry picked from commit 4ef351aa3467a587e03d8d19cdd9f280ab8fff4d)

Review-Url: https://codereview.chromium.org/2680933007 .
Cr-Commit-Position: refs/branch-heads/2987@{#423}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}

[modify] https://crrev.com/8d5792c797a0850cefd3e1d6169caf2c390b97c9/chrome/browser/ui/libgtkui/gtk_ui.cc

Tested the issue on Linux Ubuntu 14.04 using chrome beta#57.0.2987.54 version & observed Bookmarks bar, Tabs and other Chrome frame UI are with same font.
Hence adding TE Verified labels.
Please find the attached screencast for reference.

Deleted: 687770-Linux.mp4 1.7 MB

	687770-Linux.mp4 1.7 MB View Download

 Issue 698279  has been merged into this issue.

 Issue 698582  has been merged into this issue.

Just installed v57.0.2987.98 (64-bit) on openSUSE 42.1 Leap + KDE. No improvement as compared to what was reported in https://bugs.chromium.org/p/chromium/issues/detail?id=685577, same tiny fonts. 

Back to v55.

If it helps, here is the font-config-info output 

$ ./font-config-info 
Running at Fri Mar 10 21:46:10 2017

GtkSettings:
gtk-font-name        "Tahoma Regular 7"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintfull"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          122132 (119.27 DPI)

GTK 2.0 styles:
GtkLabel             "Tahoma 7"
GtkMenuItem          "Tahoma 7"
GtkToolbar           "Tahoma 7"

GSettings (org.gnome.desktop.interface):
font-name            "Cantarell 11"
text-scaling-factor  1.00

X11 display info:
screen pixels        1920x1080
screen size          367x230 mm (132.88x119.27 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintfull"
Xft.rgba             "rgb"
Xft.dpi              [unset]

XSETTINGS:
No current owner for _XSETTINGS_S0 selection
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.

Fontconfig (Tahoma 7):
requested size       7 points
family               Tahoma
pixelsize            7.29 pixels
size                 7 points
antialias            0
hinting              1
autohint             0
embeddedbitmap       0
hintstyle            3 (full)
rgba                 1 (rgb)

Fontconfig (default pattern):
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            3 (full)
rgba                 5 (none)

Fontconfig (default match):
family               Arial
pixelsize            12.50 pixels
size                 12 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       0
hintstyle            3 (full)
rgba                 1 (rgb)

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             1
embeddedbitmap       0
hintstyle            3 (full)
rgba                 1 (rgb)

Issue is reproducible on v57.0.2987.98 x64, Ubuntu 16.04 + KDE

 Issue 701198  has been merged into this issue.

I provided a workaround at #701198: use a gtkrc specifically for Google Chrome where you increase the the size of "gtk-font-name". I my case from 7 to 11.

Then launch Google Chrome with the environment variable GTK2_RC_FILES set to the custom gtkrc file.

e.g. GTK2_RC_FILES=/home/cadam/.gtkrc-2.0-google-chrome /usr/bin/google-chrome-stable %U --force-device-scale-factor=1.0" 

Re comment 43: This workaround does not work for me.

google_chrome_v55_default_gtkrc.png - This is how v55 renders menu fonts and how I expect it to work.

google_chrome_v57_default_gtkrc.png - This is how v57 (and v56) renders menu fonts with default .gtk2rc-2.0 file.

google_chrome_v57_custom_gtkrc_font_size8.png  - This is how v57 renders menu fonts with a custom .gtk2rc-2.0 file where font size in "gtk-font-name" is increased from 7 to 8. Increasing beyond 8 results in huge font sizes.

Deleted: google_chrome_v55_default_gtkrc.png 50.2 KB

	google_chrome_v55_default_gtkrc.png 50.2 KB View Download

Deleted: google_chrome_v55_default_gtkrc.png 50.2 KB

	google_chrome_v55_default_gtkrc.png 50.2 KB View Download

Deleted: google_chrome_v57_custom_gtkrc_font_size8.png 73.5 KB

	google_chrome_v57_custom_gtkrc_font_size8.png 73.5 KB View Download

Deleted: .gtkrc-2.0 426 bytes

.gtkrc-2.0 426 bytes Download

Have you passed "--force-device-scale-factor=1.0"? 

For me it works fine, as you can see from the screen shots from here: https://bugs.chromium.org/p/chromium/issues/detail?id=701198

Well, this is interesting. A couple of days ago openSUSE officially announced end of support for openSUSE Leap 42.1, so I upgraded my laptop to 42.2. The kernel/xorg stack in 42.2 no longer supports the AMD catalyst binary driver (fglrx), and so uses the radeon driver instead.

After upgrade, fonts in all apps - KDE/GTK 2.x/GTK 3.x/Google Chrome - were different. But after some fiddling with /etc/X11/xorg.d and .Xresources (creating .Xresources with "Xft.dpi: 96") I was able to achieve the same normal font sizes across all KDE/GTK 2.x/GTK 3.x apps including Google Chrome without having to use a custom GTK2_RC_FILES file.

TLDR: this issue no longer affects me.

If one runs strace on google-chrome will see in how many places google-chrome looks for gtkrc files.

I have noticed that if I have a ~/.themes/Breeze/gtk-2.0/gtkrc file, it will take precedence over GTK2_RC_FILES.

If the GTK2_RC_FILES workaround doesn't work for you, run strace and see which gtkrc files gets picked up.

Now with Chrome 59 fonts are small again! And the bad part is that the trick with GTK2_RC_FILES doesn't work anymore!

Germans have a word for this: Verschlimmbesserung!

c#48: Chrome 59 switches to GTK3, so GTK2_RC_FILES won't work any more (not sure if there's a GTK3_RC_FILES)

I do not know what you are saying.

There is no GTK3_RC_FILES anymore, but since I don't have many GTK3 applications on my KDE Neon system I was able to fix Chrome 59 by changing the font size from "Noto Sans 7" to "Noto Sans 11" in the general GTK3 config file: ~/.config/gtk-3.0/settings.ini 

In oder the see how Chrome 59 looks on my system with or without --force-device-scale-factor=1.0 I have attached a few screenshots.

My ./font-config-info configuration is:
gtk-font-name        "Noto Sans 7"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintslight"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          147456 (144,00 DPI)

GTK 2.0 styles:
GtkLabel             "Noto Sans 7"
GtkMenuItem          "Noto Sans 7"
GtkToolbar           "Noto Sans 7"

GSettings (org.gnome.desktop.interface):
font-name            "Noto Sans 7"
text-scaling-factor  1,00

X11 display info:
screen pixels        1920x1080
screen size          339x191 mm (143,86x143,62 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintslight"
Xft.rgba             "rgb"
Xft.dpi              "144"

XSETTINGS:
bash: dump_xsettings: command not found
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.

Fontconfig (Noto Sans 7):                                                                                                         
requested size       7 points
family               Noto Sans
pixelsize            14,00 pixels
size                 7 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       0
hintstyle            1 (slight)
rgba                 1 (rgb)

Fontconfig (default pattern):
antialias            [no match]
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            3 (full)
rgba                 [no match]

Fontconfig (default match):
family               Arimo
pixelsize            24,00 pixels
size                 12 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       0
hintstyle            1 (slight)
rgba                 1 (rgb)

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             0
embeddedbitmap       0
hintstyle            1 (slight)
rgba                 1 (rgb)

Deleted: chrome59_vanilla.png 212 KB

	chrome59_vanilla.png 212 KB View Download

Deleted: chrome59_force_device_scale_1_0.png 149 KB

	chrome59_force_device_scale_1_0.png 149 KB View Download

Deleted: chrome59_force_device_scale_1_0_fixed.png 161 KB

	chrome59_force_device_scale_1_0_fixed.png 161 KB View Download

The fact that these kind of fixes are required at all is crazy.
Chrome/Chromium team needs to get their shit together. In the meantime I'm
using Vivaldi because it doesn't suffer from these issues.