| [Linux] Fonts in UI elements are way too small | |||||||||||||||
| Reported by ingen...@gmail.com, May 21 2014 | Back to list | ||||||||||||||
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome after updating to v35 on Linux 2. Fonts in the bookmarks bar, tab titles, extensions, and overflow menu are too small 3. What is the expected behavior? Normal sized fonts or fonts that match the rest of the UI What went wrong? The font size is unusably small. As an example, the number in the Google Voice extension is so small it can't even be read at all. Did this work before? Yes v34 Chrome version: 35.0.1916.114 Channel: stable OS Version: Ubuntu 14.04 Flash Version: Shockwave Flash 13.0 r0 I tried resetting to both Classic theme and GTK theme, neither of which had any effect on the UI font.
,
May 21 2014
possibly (reverse) duplicate: https://code.google.com/p/chromium/issues/detail?id=318464
,
May 22 2014
Even smaller font here at 140ppi
,
May 22 2014
Also, for perspective, another screenie.
,
May 22 2014
Unable to reproduce the issue on Ubuntu 12.04 and Chrome Version: 35.0.1916.114, please review attached screenshot. Can you add a new user from chrome://settings and see if this issue is still seen in new profile.
,
May 22 2014
Same on Mint 15 Chrome Version 35.0.1916.114 - Address bar font is unusually large. Menus seem fine.
,
May 22 2014
Tried creating a new user, same issue with the new profile.
,
May 22 2014
Same on clean Ubuntu 14.04 installation and Chrome Version: 35.0.1916.114. Address bar font too large, bookmark bar font too small.
,
May 22 2014
Also having this issue. Running Arch Linux, LXDE with openbox. Fonts in the UI much smaller than they were before. Version 35.0.1916.114 (270117)
,
May 23 2014
Issue also occurring on Ubuntu 12.04.2 64bit starting with Chrome v35 - address bar font too large, extension-icon fonts very small.
,
May 23 2014
Did an over-installation of 35.0.1916.114 over 34.0.1847.137,Fonts of Wrench menu rendered fine. I am using Linux-Ubuntu 12.04-XDG_CURRENT_DESKTOP=Unity >#11 @janoside:Could you please provide your desktop environment.
,
May 23 2014
Same on openSUSE 13.1 x86-64 with Google Chrome 35.0.1916.114 and KDE 4.13.1
,
May 23 2014
On my two desktops the only thing that affects the font size in UI elements is the value of "gtk-font-name" in $HOME/gtkrc-2.0. Changing it, say, from "Tahoma Regular 8" to "Tahoma Regular 9" makes Chrome UI fonts readable, but completely messes up other GTK apps like Thunderbird or Firefox.
,
May 23 2014
Font on url bar etc WAY too large after update to 35.0.1916.114. Using Ubuntu 12.04 amd64. Help us Google.
,
May 23 2014
Same here, Ubuntu 12.04 64bit using Mate16 as a desktop environment. UI elements have tiny fonts, address bar a too large font.
,
May 23 2014
Also seeing unwelcome UI font size problems in Ubuntu 12.04 64-bit using Unity-2D: - Address bar font is much too big - Bookmark bar font size seems fine - Font size in menus seems OK, but spacing within menus seems off.
,
May 23 2014
I don't have "gtk-font-name" in $HOME/.gtkrc-2.0. The only line in that file is 'include ".gtkrc-2.0-gnome-color-chooser"'. The color-chooser file only has a line for pixmap_path and a line for "gtk-icon-sizes". Is it possible that Chrome is looking for a font attribute in this file and falls back to some default when it's not there rather than looking in other places, such as dconf?
,
May 24 2014
Chrome is completely ignoring X Window System DPI settings. For example, I use: xrandr --dpi 140 Hence, the Chrome UI font size is extremely small, almost unreadable.
,
May 24 2014
Same here. Except it's not only the address bar, all the tabs are large as well. And the dropdown on the right for profiles. All of it is so large some of it is overflowing.. Pls Fix. Thank you.
,
May 24 2014
@Google Chrome, you have 3 versions Dev(development), Beta(unstable) & stable We(people) want only best of stable version. Thanks You.
,
May 24 2014
,
May 24 2014
I am using Ubuntu 14.04 LTS, and after update to Chrome35+ all the fonts and the sizes of the tabs and the text in the omnibox increased. I tried using dconf editor to scale windows, but the changes occurs everywhere except in Chrome. Also using the scaling factor available in Display settings for Ubuntu 14.04 LTS, no change is reflected in Chrome 35+ tab sizes
,
May 25 2014
The font sizes are way too large in the address bar as well...
,
May 25 2014
Can you release the fixed version of Stable ASAP #Chrome ...?
,
May 26 2014
having the same huge font problem in the address bar as #24
,
May 26 2014
The same on Debian. Chrome 35.0.1916.114. Only menu and tabs fonts are extremely small. 34 was ok.
,
May 26 2014
Some people has to small fonts, some other too big. You broke things in Chrome 35, please revert your changes or fix this!
,
May 27 2014
The fonts being too small is a problem I haven't seen before. We have had problems before with Aura with peoples' systems missing the fonts we expect so that might be a good place to look. People complaining about fonts being too large in tabs and address bar: that is intentional in this version of Chrome. Please do not discuss fonts being too big on this bug; it confuses the issue. @mani1992msk: This change (Aura) has been on dev channel for about 3 months and beta channel for about 6 weeks. It has gone through the full testing process that all Chrome changes go through; I'm sorry we didn't catch this until it hit stable.
,
May 27 2014
@mgiuca@chromium.org Kindly revert the old change. It will be helpful to have the changes ASAP :)
,
May 27 2014
Regarding the too large font, maybe issue 377171 would be a better place to report that.
,
May 27 2014
@mani1992msk: The "change" is a complete rewrite of the UI code that has been in the works for at least 16 months (Aura). It has caused a lot of bugs, most of which we've fixed, and some of which have slipped through the cracks. We won't be reverting it, but we will hopefully have time to fix these remaining bugs in the next few releases. Apologies for the inconvenience.
,
May 27 2014
It seems the only workaronund is downgrade chrome? Where can I get chrome 34?
,
May 27 2014
@emsoft1: Is this a big enough deal to have to downgrade Chrome? From the screenshots I am seeing, the text is small; I wouldn't say "unreadable". I would strongly advise against downgrading. Old versions of Chrome will not be receiving security updates, and you will be increasingly vulnerable as time goes on. It will be difficult to find Chrome 34, but you can probably find unofficial builds of Chromium 34.
,
May 27 2014
mgiuca you are probably right, but font like this on tabs is rather annoying. Is there any known workaround without downgrading? Also I need chrome (not chromium), because of built in flash player. I wanted to downgrade, wait for fix and upgrade to recent chrome again.
,
May 27 2014
I haven't confirmed any workarounds (as I have not yet been able to reproduce the bug on any of my systems). Comment #14 suggests a workaround you could try.
,
May 27 2014
Yes, but it's not serious solution because it messes any other gtk application. I don't want to make unusable all my gtk apps because of chrome bug, sorry...
,
May 27 2014
@mgiuca: It is a big deal for anyone who is short-sighted. It is a big deal for anyone who uses other GTK-based apps like Eclipse or Thunderbird besides Chrome because the only way to make the fonts readable is at the cost of increasing them in these other GTK apps, which costs valuable display real estate. The main problem is that it is not configurable at all. Also, your previous comment mentions a missing font as a possible culprit. Which font is that - I am pretty sure both of my openSUSE desktops have all required fonts for both KDE and Gnome, including MS truetype fonts.
,
May 27 2014
Sorry, but why not to add direct settings fonts for chrome gui? Some kind of advanced settings, or possibly via extension. I believe chrome tries to get correct fonts automatically from system but it seems sometimes it fails and produce results like this.
,
May 27 2014
If it helps, here are my KDE and GTK font settings: http://i59.tinypic.com/fcma9j.jpg http://i60.tinypic.com/66kfg9.jpg http://i57.tinypic.com/2zq7d79.jpg
,
May 27 2014
I don't have gnome tweak tool (is this available on Debian?). I also have kde4, I can't remember if I have set force dpi to 96 (I'll check this). All there rest is the same.
,
May 27 2014
@mgiuca We're waiting for fix. But I don't like the tabs and the address bar does't look appealing.
,
May 27 2014
,
May 27 2014
Same problem, Kubuntu 14.04 LTS. It does indeed appear as if Chrome is ignoring the DPI value for the display, but only for menu bars. Web page fonts are the same as before, at least for me.
=== xdpyinfo: ===
screen #0:
resolution: 143x144 dots per inch
=== ~/.gtkrc-2.0: ===
# File created by KDE Gtk Config
# Configs for GTK2 programs
include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"
style "user-font"
{
font_name="Ubuntu Regular"
}
widget_class "*" style "user-font"
gtk-font-name="Ubuntu Regular 10"
gtk-theme-name="oxygen-gtk"
gtk-icon-theme-name="oxygen"
gtk-fallback-icon-theme="gnome"
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-menu-images=0
gtk-button-images=0
For comparison I'm attaching a screenshot from another well-known web browser showing the font shown at the right size. GIMP also behaves correctly.
,
May 28 2014
So from several of the comments, I'm now assuming this is a high-DPI display issue. Is anybody experiencing this on a normal DPI display? erg: Do you know anything about this? Aura supports high-DPI displays on ChromeOS, so is it just a matter of Aura not realising that it is being drawn on a high-DPI display in regular Linux? "but only for menu bars. Web page fonts are the same as before, at least for me." This is expected. Web pages are rendered by Blink; the menus and tabs are rendered by Chrome (Aura/Views).
,
May 28 2014
,
May 28 2014
I'm using the standard 96 dpi and have the issue.
,
May 28 2014
@ingenium: OK thanks; scratch that theory then.
,
May 28 2014
@ingenium: Can you report your distro name and version, as well as your desktop environment / window manager. From the look of your screenshot, it is Ubuntu Unity but I could be wrong.
,
May 28 2014
@mgiuca I'm running Ubuntu 14.04 with Unity. Upgraded from 12.04 (not a fresh install), not sure if that will make a difference.
,
May 28 2014
OK thanks. I'm quite baffled because I run Ubuntu 14.04 with Unity (and also Ubuntu 12.04 with Unity) and I have never seen this problem on the latest versions of Chrome.
,
May 28 2014
Is there a config file or anything I could send that would help? Or a debug flag that I can turn on or something that would perhaps give some insight?
,
May 28 2014
Both of my systems that have the issue have regular full HD displays (1980x1080), none of the fancy highDPI stuff.
,
May 28 2014
@mgiuca Just upgraded to v35 and have the same problem with extremely small font in menus/bars. Running xorg 1.15 on Gentoo with Xfce 4.10.1. xdpyinfo relevant info: dimensions: 1920x1080 pixels (506x285 millimeters) resolution: 96x96 dots per inch
,
May 28 2014
,
May 28 2014
@56: The font size in extension badges is issue 376335.
,
May 28 2014
The problem I'm getting with this change is that I've got font anti-aliasing turned off system-wide and yet my new Chrome UI has it enabled. This leaves my bookmarks bar and my tabs and my address bar looking blurry and just generally messy. I'm using a 24-inch 1920x1200 display at 96x96 dpi. Running Ubuntu 12.04 with KDE on top.
,
May 29 2014
I have this issue as well. Archlinux with latest Chromium. The issue is the font is hard coded as size 11. If you recompile Chromium with a bigger font size it is "fixed". Please respect xrandr font size or if that is not possible because of an arbitrary requirement for favicon heights then start displaying higher resolution favicons because most sites have them these days and if they don't they should. Aura was an important update, now let's get this fixed and put it behind us.
,
May 29 2014
Actually, Chrome > 34 on Linux is only piece of shit. Fonts unusable, java is not supported any longer. I strongly reccomend to use Chrome 34 or Firefox. You can download Chrome 34 here: http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/ But switch to normal browser like Firefox seems to be better solution, due to security issues. I think google plans do drop Linux support, dropping support for java and any other plugins are first sympthoms.
,
May 29 2014
@emsoft1: Please keep discussions on this bug relevant to the original issue, not unrelated issues like Java support (there is a thread going on the chromium-dev mailing list if you wish to discuss that). But since you brought it up: "Firefox seems to be better solution, due to security issues" -- what security issues are you talking about? The entire reason we dropped Java support is that it was a massive security risk. There are no plans to drop support for Linux; in fact Linux is ahead of the curve here, as we will be dropping NPAPI plugins on other platforms later this year.
,
May 29 2014
+asvitkine: Do you know anything about Aura font rendering and why it might be showing tiny fonts for some users on Linux?
,
May 29 2014
@mgiuca About security issue I mean firefox in compare to chrome 34. Sorry for offtopic, I only wanted to say that Chrome is going to be worse and worse on Linux (drop java support and also this bug etc.)
,
May 29 2014
@emsoft1: Please do not make the assumption that we are de-prioritizing Linux because of this. The fact is, Linux Chrome *was* getting worse and worse because every time we added or changed a piece of UI, we had to write it a second time for Linux, so the Linux port was getting out of date and missing features (for example, right-to-left text). Now that we have changed to Aura, Linux Chrome will be kept up to date with Windows Chrome, once we fix these bugs. I understand that it's frustrating that your text is small, but this failure is part of a massive commitment to supporting Linux Chrome in the future. Java support will be dropped on other platforms too; this is not a Linux-only thing.
,
May 29 2014
It appears that Chrome 35.0.1916.114 does honor the GTK+ settings, but uses the exact same font for both the menu and the tabs. The font size that's appropriate for the menu is too large the tabs. The omnibox font does not appear to be affected by these settings. For what it's worth, changing my $HOME/.gtkrc-2.0 file does seem to have any effect on my system. Instead, it looks like Chrome is taking its font configuration from the 'font-name' key in the 'org.gnome.desktop.interface' schema in dconf, but it only does so at start-up; it doesn't look like Chrome receives notifications when that key changes (as the GTK+ apps do). Until this bug gets fixed, my workaround is to manually set the system fonts smaller (such that they appear correct in the tabs; I'm fine with undersized menus since I don't open the menus that often) before starting chrome: $ gsettings set org.gnome.desktop.interface font-name 'Sans 11' Then start chrome: $ google-chrome And then restore the system fonts back to their original size, such that the other GTK+ apps appear normal: $ gsettings set org.gnome.desktop.interface font-name 'Sans 13' This can easily be automated in a wrapper script, but it would be better if this bug got fixed instead.
,
May 29 2014
In the distant past, Chrome's font code for the GTK+ port conflated sizes given in points and in pixels (see e.g. https://codereview.chromium.org/6378007). Any chance that that's what's going on here? https://developer.gnome.org/pango/stable/pango-Fonts.html#pango-font-description-set-size may be relevant.
,
May 29 2014
mgiuca: It seems on Linux, we use the font that gets returned by this:
std::string Gtk2UI::GetDefaultFontName() const {
GtkSettings* gtk_settings = gtk_settings_get_default();
CHECK(gtk_settings);
std::string out_font_name = "sans 10";
gchar* font_name = NULL;
g_object_get(gtk_settings, "gtk-font-name", &font_name, NULL);
if (font_name) {
out_font_name = std::string(font_name);
g_free(font_name);
}
return out_font_name;
}
At least, for the default font. You'll have the check the specific views code to see if indeed the default font is used for the specific controls where this is being seen.
Perhaps the g_object_get() API call is failing and we're defaulting to "sans 10" on some systems? One way to check would be to change that function to always default to "sans 10" and see if your Chrome looks like the posted screenshots.
,
May 29 2014
Chrome honors font-name but not text-scaling-factor. In practice if "gsettings get org.gnome.desktop.interface text-scaling-factor" is different from 1 the size of chrome fonts will be different from the rest of the system.
,
May 29 2014
On my openSUSE desktop $ gsettings get org.gnome.desktop.interface text-scaling-factor 1.0 and chrome's fonts are still different from the rest of the system.
,
May 29 2014
gsettings get org.gnome.desktop.interface text-scaling-factor => 1.0 gsettings get org.gnome.desktop.interface font-name => 'Cantarell 11' (With gtkrc as per my earlier comment.) Not sure why I'm getting Cantarell 11 as the font when I have Ubuntu Regular 10 in gtkrc, this GNOME junk is a mystery to me.
,
May 29 2014
Because that's what your gnome-tweak-tool's Fonts section says.
,
May 29 2014
I don't have gnome-tweak-tool. I run KDE.
,
May 29 2014
asvitkine: Yes, my ~/.gtkrc-2.0 is being parsed correctly by chrome. Changes to the font size there are reflected in chromium. However, the real issue is DPI handling. I use 140 DPI to match the native PPI of the display, and a font size of 6. Hence, the super-small text in all chromium UI elements.
,
May 29 2014
I see, so it sounds like we just need to query the scale factor from GTK and apply it to the font sizes.
,
May 29 2014
That would be optimal. I guess I can go with a wrapper script as well to dynamically toggle font size for chromium, it just seems inconvenient. Also, this needs to be DM/DE-agnostic. I have neither a display manager, nor a desktop environment. Just X Window System with i3wm.
,
May 29 2014
I wouldn't mind testing an unofficial build - to verify that the fix does work.
,
May 29 2014
FWIW, I can't get any applications (gtk2 OR gtk3) to obey changes to the text-scaling-factor in org.gnome.desktop.interface. I suspect this is likely due to my overriding both with ~/gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini?
,
May 29 2014
I think that there were issues in the past when trying to honor DPI settings in Chromium for font sizing. I believe that the finding was that many apps ignored these settings and some systems had crazy values configured as a result. It may be the case that it's just the X server's DPI setting that had this problem, and GTK's settings are fine, but be aware that changes to honor settings that weren't previously honored may break other users.
,
May 29 2014
I went with a simple wrapper for now. Works fine and doesn't disrupt other applications. I just need to give chrome a few seconds to launch with the temporary font size: #!/bin/bash sed -i.bak s/"Sans 6"/"Sans 10"/g ~/.gtkrc-2.0 google-chrome-stable & echo "Reverting font..." sleep 5 sed -i.bak s/"Sans 10"/"Sans 6"/g ~/.gtkrc-2.0
,
May 29 2014
There may have been some confusion in previous comments regarding the dpi value. Instead of using xdpyinfo (like previous comments did), font dpi should be found by xrdb: "xrdb -q | grep Xft.dpi" (default 96). This should be cross-DE.
,
May 29 2014
@massimo Yes, xrdb approach gives the different result compared to xdpyinfo: $ xrdb -q | grep Xft.dpi Xft.dpi: 144 $ xdpyinfo | grep resolution resolution: 96x96 dots per inch $ The first one seems to be correct for my screen dimensions 1920x1080 pixels (506x285 millimeters)
,
May 29 2014
@massimo: On my home laptop (full HD 17'' display): $ xrdb -q | grep -i Xft Xft.antialias: 1 Xft.hinting: 1 Xft.hintstyle: hintfull Xft.rgba: rgb vadymk@firefly ~ $ xdpyinfo | grep resol resolution: 133x119 dots per inch I'll post the data from the office desktop tomorrow.
,
May 29 2014
$ xdpyinfo | grep resol resolution: 96x96 dots per inch $ xrdb -q | grep -i Xft Xft.antialias: 1 Xft.dpi: 96 Xft.hinting: 1 Xft.hintstyle: hintfull Xft.rgba: none
,
May 29 2014
I finally got around to writing a program that dumps pretty much all the font-related settings that I'm aware of: https://github.com/derat/font-config-info Might be useful for debugging things like this; let me know if there's anything else I should add.
,
May 30 2014
This was what the above utility returned for me: Running at Thu May 29 18:08:39 2014 GtkSettings: gtk-font-name "DejaVu Sans 8" gtk-xft-antialias 1 (yes) gtk-xft-hinting 1 (yes) gtk-xft-hintstyle "hintfull" gtk-xft-rgba "none" gtk-xft-dpi 98304 (96.00 DPI) GSettings (org.gnome.desktop.interface): font-name "DejaVu Sans 8" text-scaling-factor 1.00 X11 display info: screen pixels 1600x900 screen size 423x238 mm (96.08x96.05 DPI) X resources (xrdb): Xft.antialias "1" Xft.hinting "1" Xft.hintstyle "hintfull" Xft.rgba "none" Xft.dpi "96" Fontconfig (default match): FC_ANTIALIAS 1 FC_HINTING 1 FC_AUTOHINT 0 FC_HINT_STYLE 1 (slight) FC_RGBA 5 (none)
,
May 30 2014
Some good news: fonts looks fine on my desktop that has a 23" monitor running at 2048 x 1152. I configure X with the actual screen size (via xorg.conf) and X calculates the DPI to be 101 x 102. From X.log: (**) RADEON(0): Display dimensions: (510, 286) mm (**) RADEON(0): DPI set to (101, 102) However, xrdb reports nothing about DPI, which seems weird. I'm using Gentoo Linux with KDE4. (Tangential note: the menu has no icons in 35, is there an issue for this or is it a feature?)
,
May 30 2014
$ ./font-config-info Running at Thu May 29 21:32:06 2014 GtkSettings: gtk-font-name "Droid Sans 6" gtk-xft-antialias 1 (yes) gtk-xft-hinting 1 (yes) gtk-xft-hintstyle "hintfull" gtk-xft-rgba "rgb" gtk-xft-dpi 143611 (140.25 DPI) GSettings (org.gnome.desktop.interface): font-name "Cantarell 11" text-scaling-factor 1.00 X11 display info: screen pixels 1440x900 screen size 261x163 mm (140.14x140.25 DPI) X resources (xrdb): Xft.antialias [unset] Xft.hinting [unset] Xft.hintstyle [unset] Xft.rgba [unset] Xft.dpi [unset] Fontconfig (default match): FC_ANTIALIAS 1 FC_HINTING 1 FC_AUTOHINT 0 FC_HINT_STYLE 3 (full) FC_RGBA 1 (rgb)
,
May 30 2014
Then the bad news is that they do look too small on my laptop, which has a 12" screen and runs at 1280 x 800 yielding a DPI of 124 x 123, which also runs Gentoo and KDE4. Sorry I didn't get a chance to install the font-info program but if it will help I'll do it later.
,
May 30 2014
On my home laptop: Running at Fri May 30 07:42:21 2014 GtkSettings: gtk-font-name "Tahoma Regular 9" 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) 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] Fontconfig (default match): FC_ANTIALIAS 1 FC_HINTING 1 FC_AUTOHINT 0 FC_HINT_STYLE 3 (full) FC_RGBA 1 (rgb) On my work desktop (dual-monitor setup): $ ./font-config-info Running at Fri May 30 08:56:55 2014 GtkSettings: gtk-font-name "Tahoma Regular 8" gtk-xft-antialias 1 (yes) gtk-xft-hinting 1 (yes) gtk-xft-hintstyle "hintfull" gtk-xft-rgba "rgb" gtk-xft-dpi 98304 (96.00 DPI) GSettings (org.gnome.desktop.interface): font-name "Cantarell 10" text-scaling-factor 1.00 X11 display info: screen pixels 3840x1080 screen size 1060x301 mm (92.02x91.14 DPI) X resources (xrdb): Xft.antialias "1" Xft.hinting "1" Xft.hintstyle "hintfull" Xft.rgba "rgb" Xft.dpi "96" Fontconfig (default match): FC_ANTIALIAS 1 FC_HINTING 1 FC_AUTOHINT 1 FC_HINT_STYLE 3 (full) FC_RGBA 1 (rgb)
,
May 31 2014
I have 236 DPI display (dell laptop) and google chrome 36.0.1985.32 menus, tabs are SO TINY that I'm unable to read these (unless I'm close to the screen like 10cm). $ ./font-config-info Running at Sat May 31 22:02:38 2014 GtkSettings: gtk-font-name "Liberation Sans 22" gtk-xft-antialias 1 (yes) gtk-xft-hinting 1 (yes) gtk-xft-hintstyle "hintslight" gtk-xft-rgba "rgb" gtk-xft-dpi 241664 (236,00 DPI) GSettings (org.gnome.desktop.interface): GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. font-name "Cantarell 11" text-scaling-factor 1,00 X11 display info: screen pixels 3200x1800 screen size 345x194 mm (235,59x235,67 DPI) X resources (xrdb): Xft.antialias "1" Xft.hinting "1" Xft.hintstyle "hintslight" Xft.rgba "rgb" Xft.dpi "236" Fontconfig (default match): FC_ANTIALIAS 1 FC_HINTING 1 FC_AUTOHINT 0 FC_HINT_STYLE 1 (slight) FC_RGBA 1 (rgb) Only text in menus/tabs are problematic. For web pages I'm simply using 200% zoom.
,
Jun 1 2014
So is this confirmed bug?
,
Jun 1 2014
Tried HiDPI support in chromium under Linux (by enabling enable_hidpi=1 for Linux and rebuilding). Fonts with HiDPI enabled are readable size, much better. Unfortunately everything is veeeery slow then. Also menu is not displayed properly. I hope it can be fixed for Linux. In mean time being able to set bigger default font for UI would be a very desired workaround.
,
Jun 1 2014
Update to comment #93. Looks like slowness/weirdness is also happening with this build without HIDPI (likely some local issue) So there is a chance that enabling hidpi (+testing and possibly small fixes) for Linux will actually solve this bug.
,
Jun 1 2014
That's awesome news. Do you know if the font scaling works with HiDPI?
,
Jun 1 2014
Fonts are scalled if that is what you are asking for. Here are two screenshots. Done on 35.0.1916.114, zoom on 100%. This one for chromium build with enable_hidpi=1 http://ixion.pld-linux.org/~arekm/chromium-hidpi-on.jpg This with enable_hidipi=0 http://ixion.pld-linux.org/~arekm/chromium-hidpi-off.jpg
,
Jun 1 2014
I have a similar huge font issue but all the menus not sized large enough for the contents as shown.
./font-config-info
Running at Sun Jun 1 19:56:50 2014
GtkSettings:
gtk-font-name "Ubuntu 9"
gtk-xft-antialias 1 (yes)
gtk-xft-hinting 1 (yes)
gtk-xft-hintstyle "hintmedium"
gtk-xft-rgba "[unset]"
gtk-xft-dpi 98304 (96.00 DPI)
GSettings (org.gnome.desktop.interface):
font-name "Cantarell 11"
text-scaling-factor 1.00
X11 display info:
screen pixels 2560x1440
screen size 677x381 mm (96.05x96.00 DPI)
X resources (xrdb):
Xft.antialias [unset]
Xft.hinting "1"
Xft.hintstyle "hintmedium"
Xft.rgba [unset]
Xft.dpi [unset]
Fontconfig (default match):
FC_ANTIALIAS 1
FC_HINTING 1
FC_AUTOHINT 0
FC_HINT_STYLE 2 (medium)
FC_RGBA 5 (none)
Ver: 35.0.1870
,
Jun 3 2014
As is often the case, I suspect that multiple unrelated-in-cause font rendering bugs are being discussed here. As this issue nears 100 comments, here is an attempt to make sense of it: - In some cases, a high-DPI display is being used (e.g. gtk-xft-dpi reports 236 DPI as in comment #91), and Chrome doesn't scale fonts (or any other parts of the UI) accordingly. This is easy to reproduce by e.g. running Xephyr with -dpi 236. Some people have partially worked around it by jacking up the zoom setting for web content, but Chrome should instead scale both the UI and web content appropriately in this case. This is a known problem that's being tracked at issue 143619 -- please star it if you want status updates. - The size of the font used in the omnibox is slightly larger than the font used in tabs and menus. This came along with the move to Aura and is unlikely to change. - In a few cases, all UI components (fonts in tabs and menus, toolbar icons, etc.) are huge relative to other apps, as in comment #98. In the screenshots that I've looked at, Chrome appears to be using high-DPI assets when it shouldn't be. I'm not sure what causes this -- per issue 143619, I don't think that high-DPI mode is detected automatically.
,
Jun 3 2014
"The size of the font used in the omnibox is slightly larger than the font used in tabs and menus. This came along with the move to Aura and is unlikely to change." Nope. Fonts in omnibox are correct. Fonts on tab and menu are not "sligtly" smaller. They are much smaller and it should be treated as bug. I hava standard display, standard dpi 96x96. It's serious issue.
,
Jun 3 2014
Regarding point #1 there, it is not just high DPI displays. It affects standard 96 DPI displays as well.
,
Jun 3 2014
Indeed, it's not caused by any non standard configuration. And I can say again: this "feature" was introduced on Chrome 35, I hope it will be fixed soon.
,
Jun 3 2014
Please understand that the "UI text is tiny" issue does not appear on all 96-DPI systems -- see the attached screenshot, for instance. There's no way to fix this until it's known why some systems are using a tiny font while other systems a using a normal font. If you have a non-high-DPI display and would like to help track that down, please do the following: 1. Take a screenshot demonstrating the problem (ideally including text from the omnibox, tab strip, menu, and web content). 2. Compile and run https://github.com/derat/font-config-info and save its output. 3. Go to http://new.crbug.com/ and file a new bug with the screenshot, font-config-info output, and the "Google Chrome:" line from chrome://version. 4. Add a comment to this issue with the ID of the bug that you just filed.
,
Jun 4 2014
Derat: why are you asking for creating new bug report? It's reported here already. Also you have a lot of screenshots here (including the one I provided). I have no idea what causes this bug, but you can eaisly get the same behaviour, for example on clean debian sid with kde. So it's not so difficult to reproduce
,
Jun 4 2014
Derat: the information you're asking for is already present in this bug.
,
Jun 4 2014
Don't know if this is related, but in addition to the fonts being too small I can't get skandinavian letters, like A and O with two dots, when using chrome. I have Finnish on top in the chrome settings and they're fine everywhere else.
,
Jun 4 2014
google-chrome --force-device-scale-factor=2 ALMOST works (tabs corrupted, bad menu size) on high DPI display under Linux but well, I hope issue 143619 gets proper attention from chromium devs.
,
Jun 5 2014
If anyone experiencing small UI fonts on a non-high-DPI display is set up to do their own builds of Chromium, I'd be interested in seeing the "DEBUG" messages that are logged to stderr after patching in https://codereview.chromium.org/318713005/, along with your system's output from https://github.com/derat/font-config-info and a screenshot showing the sizing of Chrome's UI fonts vs. gedit's fonts. LocationBarView::Init() scales the omnibox font up to 16px to match the size of the omnibox assets. Tab::InitTabResources() calls ui::ResourceBundle::GetFont(ui::ResourceBundle::BaseFont), which goes to PlatformFontPango, which goes to Gtk2UI::GetDefaultFontName(), which looks up the gtk-font-name property in GtkSettings. The value of that property is passed to pango_font_description_from_string(), described here: https://developer.gnome.org/pango/stable/pango-Fonts.html#pango-font-description-from-string . The format of the string is usually "FAMILY SIZE", where SIZE is interpreted as pixels if suffixed with "px" or as points otherwise. ingenium: Per comment #86, gtk-font-name is set to "DejaVu Sans 8". With a 1600x900 display at 96 DPI and 72 points/inch, an 8-point font should be 10.67 pixels tall, which is quite small. It'd be interesting to see if you get different results after changing the font size to be configured in pixels instead. Could you attach a screenshot showing the size of the fonts used by a GTK+ app like gedit?
,
Jun 5 2014
derat: Sure, attached is a screenshot with gedit on top of Chrome. You can see the fonts in Chrome are smaller.
,
Jun 5 2014
derat: Here's another comparison screenie. gnome-calculator & prefs, tabs, bookmark bar, and a bookmark dialog. I sure hope the fix for this only applies to font sizes. I've seen mention of scaling UI elements in the high-DPI bug report. I sure don't want any graphical UI elements scaled up ala Windows DPI scaling mechanism.
,
Jun 7 2014
Problem displaying small or large font is linked chrome / chromium strictly to GTK +. To resolve difficulties install kde-gtk-config. In the options, color themes layout settings button appears - Configuring GTK +. In this setting, select the desired font that will be picked up automatically by all applications attachment to the GTK + including Chrome / Chromium. Good Luck.
,
Jun 7 2014
For my later comment screenshot.
,
Jun 7 2014
@CyberCp..: The problem is that Chrome's font sizes are different to those in all other GTK appps, and that it appeared with the switch to Aura from GTK in v35. I have kde-gtk-config installed and changing font size there affects all GTK apps the same way - unlike chrome v35.
,
Jun 7 2014
My issue was lack of anti-aliasing/incorrect fonts in Chrome 35.0.1916.114. After tinkering for a while this tool resolved it for me: https://launchpad.net/~no1wantdthisname/+archive/ppa Could be of help to anyone affected and hint at the actual issue.
,
Jun 9 2014
Meanwhile on XFCE with Chrome 35.0.1916.114 all the text is HUGE.
,
Jun 12 2014
For me, the solution in #114 fixed a font kerning issue but the font size is still huge and menus messed up as before #98
,
Jun 12 2014
It's time for chtomium team to consider changing their font rendering engine. Everybody use many, many apps. But Chrome is the only one having strange behaviour like this. Huge fonts, small fonts but almost never ok. So are you going to rewrite your gui framework to get fonts handled correctly? Stop saying that there is no any bug, it starts to look like very annoying.
,
Jun 14 2014
Why the "Ctrl + Z" is not working on address bar ??
,
Jun 14 2014
My fonts are also too small on Chrome. I work on Ubuntu 14.01. Can't set it up correctly!
,
Jun 30 2014
Adding my own screenshot for chrome vs chromium on linux. The bookmark bar and tab title fonts are very large on Chrome v35 as you can see. Running xfwm (and xfce). It is a little disappointing that chrome/chromium are the only applications I use regularly that don't respect the desktop environment font. Firefox and my terminals etc, do fine with this.
,
Jul 3 2014
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9816ff759cec9ef4b8774b649c695cd9d51ade80 commit 9816ff759cec9ef4b8774b649c695cd9d51ade80 Author: derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Date: Thu Jul 03 07:50:39 2014 linux: Get UI font from GtkLabel style. Make Gtk2UI use the Pango font description from GtkLabel's style rather than the gtk-font-name property from GtkSettings. Also log an error if the two values differ. BUG=375824 Review URL: https://codereview.chromium.org/368483002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@281219 0039d316-1c4b-4281-b951-d872f2087c98
,
Jul 3 2014
------------------------------------------------------------------ r281219 | derat@chromium.org | 2014-07-03T07:50:39.974153Z Changed paths: M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/libgtk2ui/gtk2_ui.cc?r1=281219&r2=281218&pathrev=281219 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/libgtk2ui/gtk2_ui.h?r1=281219&r2=281218&pathrev=281219 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_pango.cc?r1=281219&r2=281218&pathrev=281219 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/linux_font_delegate.h?r1=281219&r2=281218&pathrev=281219 linux: Get UI font from GtkLabel style. Make Gtk2UI use the Pango font description from GtkLabel's style rather than the gtk-font-name property from GtkSettings. Also log an error if the two values differ. BUG=375824 Review URL: https://codereview.chromium.org/368483002 -----------------------------------------------------------------
,
Jul 3 2014
r281219 changes where Chrome gets its default UI font. I don't know whether it will fix the sizing issues with the fonts used in tabs and the menu, since I'm still unaware of any steps to reproduce this issue on systems that aren't currently exhibiting the problem, but I figure it's worth a shot. The change should be present in the build that's available at https://download-chromium.appspot.com/?platform=Linux_x64, and I'm curious about whether people with small fonts on normal-DPI displays still see the problem when downloading and extracting that file, switching to its "chrome-linux" directory, and running "./chrome --user-data-dir=/tmp/chrome" (i.e. *without* adding any additional flags or changing Chromium's settings from the default). Regardless of whether it fixes the problem, I'm interested in whether a message starting with "Font specified in gtk-font-name property" gets logged to stderr when you run that version of Chromium, and in what the message says. If it's still broken with that change, please also attach a screenshot (ideally comparing Chromium to another GTK app like gedit), the "Font specified in gtk-font-name property" log message if any, and the output of https://github.com/derat/font-config-info (which I've updated to log more information about GTK styles).
,
Jul 3 2014
Output of fontconfig from my office desktop is in comment #90. $ CHROME_DEVEL_SANDBOX=/usr/local/sbin/chrome-devel-sandbox ./chrome --user-data-dir=/tmp/chrome1 Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected Fontconfig warning: "~/.fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected [16683:16683:0703/150829:ERROR:gtk2_ui.cc(839)] Font specified in gtk-font-name property (Tahoma Regular 8) does not match font from GtkLabel (Tahoma 8); see http://crbug.com/375824 [16683:16710:0703/150829:ERROR:nss_util.cc(856)] After loading Root Certs, loaded==false: NSS error code: -8018 Screenshot comparing with gedit is attached.
,
Jul 3 2014
So the issue is not fixed on my system.
,
Jul 3 2014
Output from the latest font-config-info:
$ ./font-config-info
Running at Thu Jul 3 15:43:24 2014
GtkSettings:
gtk-font-name "Tahoma Regular 8"
gtk-xft-antialias 1 (yes)
gtk-xft-hinting 1 (yes)
gtk-xft-hintstyle "hintfull"
gtk-xft-rgba "rgb"
gtk-xft-dpi 98304 (96.00 DPI)
GTK 2.0 styles:
GtkLabel "Tahoma 8"
GtkMenuItem "Tahoma 8"
GtkToolbar "Tahoma 8"
GSettings (org.gnome.desktop.interface):
font-name "Cantarell 10"
text-scaling-factor 1.00
X11 display info:
screen pixels 3840x1080
screen size 1060x301 mm (92.02x91.14 DPI)
X resources (xrdb):
Xft.antialias "1"
Xft.hinting "1"
Xft.hintstyle "hintfull"
Xft.rgba "rgb"
Xft.dpi "96"
XSETTINGS:
sh: dump_xsettings: command not found
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.
Fontconfig (default match):
Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "~/.fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected
FC_ANTIALIAS 1
FC_HINTING 1
FC_AUTOHINT 1
FC_HINT_STYLE 3 (full)
FC_RGBA 1 (rgb)
,
Jul 3 2014
vkrevs@: Thanks. Would you mind attaching your ~/.fonts.conf file and the output from "fc-match -v 'Tahoma 8'"? My only theory at the moment is that there's additional customization happening via FontConfig, which I don't believe is queried when rendering UI text (see issue 125235).
,
Jul 3 2014
derat@: This dev build fixes font issue on my system (3.12.13-gentoo x86_64, Xfce 4.10.1). Had to set CHROME_DEVEL_SANDBOX env variable. The stderr does not have anything related to gtk-font-name: star@narwhal chrome-linux $ ./chrome --user-data-dir=/tmp/chrome ATTENTION: default value of option force_s3tc_enable overridden by environment. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [17964:17964:0703/144559:ERROR:sync_control_vsync_provider.cc(60)] glXGetSyncValuesOML should not return TRUE with a media stream counter of 0. Thanks for your efforts
,
Jul 3 2014
sergey.starosek@: Thanks for the feedback! Just to confirm, were you previously seeing small fonts in the tab strip and menu? I'm experimenting with making PlatformFontPango query FontConfig for the font size in addition to the family, with the suspicion that some users seeing this problem may have FontConfig configurations that are increasing the size of the font that's configured in GTK.
,
Jul 3 2014
derat@: output of fc-match -v 'Tahoma 8' attached.
,
Jul 3 2014
derat@: .fonts.conf attached.
,
Jul 3 2014
vkrevs@: Thanks, it looks like your .fonts.conf is disabling AA on "Tahoma 8". Mind updating font-config-info and running it one more time? I've updated it to pass GtkLabel's font family and size to FontConfig. If the results returned by FontConfig look reasonable, perhaps it'd be possible to do the same within Chrome (at which point I think this is just issue 125235).
,
Jul 3 2014
@derat: with v36 I had that small fonts problem. see my comments #54 and #81
,
Jul 7 2014
@derat: sorry for the delay. here is the output of the latest font-config-info: $ ./font-config-info Running at Mon Jul 7 08:50:35 2014 GtkSettings: gtk-font-name "Tahoma Regular 8" gtk-xft-antialias 1 (yes) gtk-xft-hinting 1 (yes) gtk-xft-hintstyle "hintfull" gtk-xft-rgba "rgb" gtk-xft-dpi 98304 (96.00 DPI) GTK 2.0 styles: GtkLabel "Tahoma 8" GtkMenuItem "Tahoma 8" GtkToolbar "Tahoma 8" GSettings (org.gnome.desktop.interface): font-name "Cantarell 10" text-scaling-factor 1.00 X11 display info: screen pixels 3840x1080 screen size 1060x301 mm (92.02x91.14 DPI) X resources (xrdb): Xft.antialias "1" Xft.hinting "1" Xft.hintstyle "hintfull" Xft.rgba "rgb" Xft.dpi "96" XSETTINGS: sh: dump_xsettings: command not found Install dump_xsettings from https://code.google.com/p/xsettingsd/ to print this information. Fontconfig (Tahoma 8): requested size 8 points at 96.00 DPI Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected Fontconfig warning: "~/.fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected FC_FAMILY "Tahoma" FC_PIXEL_SIZE 8.33 pixels FC_SIZE 8 points FC_ANTIALIAS 0 FC_HINTING 1 FC_AUTOHINT 0 FC_HINT_STYLE 3 (full) FC_RGBA 1 (rgb)
,
Jul 10 2014
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dd06564986bdc86b90e6ea2a87dbadb019da2345 commit dd06564986bdc86b90e6ea2a87dbadb019da2345 Author: derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Date: Thu Jul 10 01:03:41 2014 linux: Round font sizes when going from points to pixels. Round point-based Pango font sizes to the nearest pixel. Otherwise, we can end up with smaller UI fonts than GTK+ 2.0 apps in some cases. This seems to be in line with what get_scaled_size() does in Pango's pango/pangofc-fontmap.c, and gives me identically sized text in Gimp 2.6.12 and Chrome when I set the Gtk/FontName XSETTINGS property to "Arial 10". Note that Chrome doesn't currently honor additional fine-grained configuration performed via FontConfig, like disabling antialiasing for fonts of a certain size. That'll happen in a separate change. BUG=375824 Review URL: https://codereview.chromium.org/377413002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282204 0039d316-1c4b-4281-b951-d872f2087c98
,
Jul 10 2014
------------------------------------------------------------------ r282204 | derat@chromium.org | 2014-07-10T01:03:41.079881Z Changed paths: M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/pango_util.cc?r1=282204&r2=282203&pathrev=282204 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/pango_util.h?r1=282204&r2=282203&pathrev=282204 linux: Round font sizes when going from points to pixels. Round point-based Pango font sizes to the nearest pixel. Otherwise, we can end up with smaller UI fonts than GTK+ 2.0 apps in some cases. This seems to be in line with what get_scaled_size() does in Pango's pango/pangofc-fontmap.c, and gives me identically sized text in Gimp 2.6.12 and Chrome when I set the Gtk/FontName XSETTINGS property to "Arial 10". Note that Chrome doesn't currently honor additional fine-grained configuration performed via FontConfig, like disabling antialiasing for fonts of a certain size. That'll happen in a separate change. BUG=375824 Review URL: https://codereview.chromium.org/377413002 -----------------------------------------------------------------
,
Jul 11 2014
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6b2e23739cf05dbd8013c63464a5f69c5facb2a1 commit 6b2e23739cf05dbd8013c63464a5f69c5facb2a1 Author: derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Date: Fri Jul 11 21:21:18 2014 Apply hinting in SkiaTextRenderer::SetFontRenderParams(). Make SetFontRenderParams() pass the hinting setting through to SkPaint instead of exposing a separate SetFontHinting() method. Also add a default c'tor for FontRenderParams and pass its autohinter setting through to SkPaint as well. BUG=125235,375824 Review URL: https://codereview.chromium.org/387743002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282703 0039d316-1c4b-4281-b951-d872f2087c98
,
Jul 11 2014
------------------------------------------------------------------ r282703 | derat@chromium.org | 2014-07-11T21:21:18.033538Z Changed paths: M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params_linux.cc?r1=282703&r2=282702&pathrev=282703 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/render_text_pango.cc?r1=282703&r2=282702&pathrev=282703 A http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params.cc?r1=282703&r2=282702&pathrev=282703 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params.h?r1=282703&r2=282702&pathrev=282703 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/gfx.gyp?r1=282703&r2=282702&pathrev=282703 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/render_text.cc?r1=282703&r2=282702&pathrev=282703 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params_win.cc?r1=282703&r2=282702&pathrev=282703 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/render_text.h?r1=282703&r2=282702&pathrev=282703 Apply hinting in SkiaTextRenderer::SetFontRenderParams(). Make SetFontRenderParams() pass the hinting setting through to SkPaint instead of exposing a separate SetFontHinting() method. Also add a default c'tor for FontRenderParams and pass its autohinter setting through to SkPaint as well. BUG=125235,375824 Review URL: https://codereview.chromium.org/387743002 -----------------------------------------------------------------
,
Jul 14 2014
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1e8f699bfc66280866ab999cdacaae424b2c3658 commit 1e8f699bfc66280866ab999cdacaae424b2c3658 Author: derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Date: Mon Jul 14 19:40:55 2014 ui/gfx: Allow for font-specific rendering settings. Let implementations attach a FontRenderParams to a gfx::PlatformFont rather than using a single default everywhere. On Linux and Chrome OS, query FontConfig for font-specific rendering settings. BUG=125235,375824 TBR=jorgelo@chromium.org Review URL: https://codereview.chromium.org/382273002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283001 0039d316-1c4b-4281-b951-d872f2087c98
,
Jul 14 2014
------------------------------------------------------------------ r283001 | derat@chromium.org | 2014-07-14T19:40:55.051475Z Changed paths: M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params_linux.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_win.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_win.h?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_mac.h?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/render_text_harfbuzz.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_pango.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/render_text_win.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_pango.h?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/pango_util.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/render_text_pango.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/sandbox_ipc_linux.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_ios.mm?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params_android.cc?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font.h?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/font_render_params.h?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font.h?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_mac.mm?r1=283001&r2=283000&pathrev=283001 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/platform_font_ios.h?r1=283001&r2=283000&pathrev=283001 ui/gfx: Allow for font-specific rendering settings. Let implementations attach a FontRenderParams to a gfx::PlatformFont rather than using a single default everywhere. On Linux and Chrome OS, query FontConfig for font-specific rendering settings. BUG=125235,375824 TBR=jorgelo@chromium.org Review URL: https://codereview.chromium.org/382273002 -----------------------------------------------------------------
,
Jul 16 2014
vkrevs: Mind giving it one more shot with a new build as described in comment #123?
,
Jul 16 2014
derat: Here it is - looks very good: $ CHROME_DEVEL_SANDBOX=/usr/local/sbin/chrome_devel_sandbox ./chrome --user-data-dir=/tmp/chrome1 Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected Fontconfig warning: "~/.fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected [6852:6852:0716/094435:ERROR:gtk2_ui.cc(839)] Font specified in gtk-font-name property (Tahoma Regular 8) does not match font from GtkLabel (Tahoma 8); see http://crbug.com/375824
,
Jul 16 2014
Great, looks like it's working! Anyone else with a normal-DPI display who was seeing smaller UI fonts in Chrome than in other GTK apps: please let me know if the problem is still present when you do the following: wget -O chrome.zip https://download-chromium.appspot.com/dl/Linux_x64 unzip chrome.zip cd chrome-linux ./chrome --user-data-dir=/tmp/chrome
,
Jul 16 2014
% ./chrome --user-data-dir=/tmp/chrome [24515:24515:0716/094742:FATAL:browser_main_loop.cc(158)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. zsh: abort (core dumped) ./chrome --user-data-dir=/tmp/chrome Nothing missing according to ldd.
,
Jul 16 2014
meta404: Hmm, try "./chrome --user-data-dir=/tmp/chrome --disable-setuid-sandbox".
,
Jul 17 2014
I can confirm that the posted build works for me, fonts are the correct size again. Too bad it wasn't able to be included in v36 which came out today.
,
Jul 17 2014
Yes, but I'm sure it will be in the next release. Unless there is reason to believe otherwise?
,
Jul 17 2014
The 37 branch happened weeks ago, but I'm hopeful that the smaller parts of this can be merged: https://codereview.chromium.org/368483002/ https://codereview.chromium.org/377413002/
,
Jul 17 2014
OK, got it to run with --disable-setuid-sandbox. Fonts are still tiny. I get a message in the console: [15488:15488:0717/092748:ERROR:gtk2_ui.cc(839)] Font specified in gtk-font-name property (Ubuntu 9) does not match font from GtkLabel (Ubuntu 9); see http://crbug.com/375824
,
Jul 17 2014
Problem solved for me with the build in #143, on a normal-DPI display (96x96).
,
Jul 17 2014
meta404: Could you also paste the output from https://github.com/derat/font-config-info ?
,
Jul 17 2014
Running at Thu Jul 17 12:47:40 2014 GtkSettings: gtk-font-name "Ubuntu 9" gtk-xft-antialias 1 (yes) gtk-xft-hinting 1 (yes) gtk-xft-hintstyle "hintmedium" gtk-xft-rgba "rgb" gtk-xft-dpi 147456 (144,00 DPI) GTK 2.0 styles: GtkLabel "Ubuntu 9" GtkMenuItem "Ubuntu 9" GtkToolbar "Ubuntu 9" GSettings (org.gnome.desktop.interface): font-name "Cantarell 11" text-scaling-factor 1,00 X11 display info: screen pixels 3200x1080 screen size 568x191 mm (143,10x143,62 DPI) X resources (xrdb): Xft.antialias "1" Xft.hinting "1" Xft.hintstyle "hintmedium" Xft.rgba "rgb" Xft.dpi "144" XSETTINGS: sh: 1: set: Illegal option -o pipefail Install dump_xsettings from https://code.google.com/p/xsettingsd/ to print this information. Fontconfig (Ubuntu 9): requested size 9 points at 96,00 DPI family Ubuntu pixelsize 9,38 pixels size 9 points antialias 1 hinting 1 autohint 0 hintstyle 2 (medium) rgba 1 (rgb)
,
Jul 17 2014
-o pipefail is indeed an illegal option for the set command in dash. I tried building dump_xsettings, but it just says No current owner for _XSETTINGS_S0 selection
,
Jul 18 2014
meta404: Thanks. I suspect that what you're seeing is a DPI-related issue. In your output from font-config-info, the X server and gtk-xft-dpi both claim 144 DPI. Chrome currently uses Pango's DPI setting as reported by pango_cairo_context_get_resolution(); if Pango reports 0 or a negative value, we default to 96 DPI instead. I suspect that that's what's happening on your system. I think that Chrome's ui/gfx/pango_util.cc file makes the assumption that a PangoContext created via pango_font_map_create_context(pango_cairo_font_map_get_default()) will have a properly-set resolution. Perhaps this was true at some point in the past (e.g. maybe this context came from GTK before), but it doesn't seem to be the case anymore. I'll write a small change to use the value from gtk-xft-dpi to convert from points to pixels to see if that resolves the issue. As a workaround and as a way to test this theory, you could try specifying your desired UI font in pixels instead of points. 9 points at 144 DPI corresponds to 13.5 pixels. Does configuring GTK to use "Ubuntu 13px" or "Ubuntu 14px" instead of "Ubuntu 9" result in identically-sized text between Chrome and GTK apps?
,
Jul 18 2014
Not sure how I'd configure GTK for "Ubuntu Regular 14px". Usually KDE generates a .gtkrc-2.0 for me. I tried editing it, but it didn't seem to make any difference.
,
Jul 18 2014
meta404: I think that https://codereview.chromium.org/406493002/ will fix the problem you're seeing (at least, it does for me when I request "Ubuntu 9" after I configure X and gtk-xft-dpi to report 144 DPI). I'll let you know when it's checked in, if you'd be able to re-test with an updated build then.
,
Jul 18 2014
------------------------------------------------------------------ r284121 | derat@chromium.org | 2014-07-18T16:29:52.592836Z Changed paths: M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/libgtk2ui/gtk2_ui.cc?r1=284121&r2=284120&pathrev=284121 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/libgtk2ui/gtk2_ui.h?r1=284121&r2=284120&pathrev=284121 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/linux_font_delegate.h?r1=284121&r2=284120&pathrev=284121 M http://src.chromium.org/viewvc/chrome/trunk/src/ui/gfx/pango_util.cc?r1=284121&r2=284120&pathrev=284121 linux: Get font DPI from GTK. Use GtkSettings's gtk-xft-dpi property to convert Pango font descriptions from points to pixels. Previously PangoContext's default resolution, which is sometimes (always?) unset, was used, resulting in 96 DPI being used for conversions regardless of the value reported by X. BUG=375824 Review URL: https://codereview.chromium.org/406493002 -----------------------------------------------------------------
,
Jul 18 2014
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ccf6a5b847c59446baf30c1e57fa993d2f059c96 commit ccf6a5b847c59446baf30c1e57fa993d2f059c96 Author: derat@chromium.org <derat@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Date: Fri Jul 18 16:29:52 2014 linux: Get font DPI from GTK. Use GtkSettings's gtk-xft-dpi property to convert Pango font descriptions from points to pixels. Previously PangoContext's default resolution, which is sometimes (always?) unset, was used, resulting in 96 DPI being used for conversions regardless of the value reported by X. BUG=375824 Review URL: https://codereview.chromium.org/406493002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@284121 0039d316-1c4b-4281-b951-d872f2087c98
,
Jul 18 2014
meta404: Please let me know if things look better in a new download of https://download-chromium.appspot.com/dl/Linux_x64 .
,
Jul 18 2014
Yes! That fixes it. Good work!
,
Jul 21 2014
I'm unsure exactly what needs to be merged here - at this point, what revisions is the request for? I'm also not thrilled that we had to make additional changes after the merge request was made, should we anticipate seeing additional merge requests or is this closed now? Why can't this wait until M38 (given that it has been an issue since M35)?
,
Jul 21 2014
#148 was my merge request. I'm okay with waiting for 38 since there's a workaround (configuring one's system to request a font size in pixels rather than points).
,
Jul 21 2014
,
Jul 24 2014
Issue 368786 has been merged into this issue.
,
Aug 2 2014
I just installed Chrome 38 unstable. Indeed small funt bug is fixed. But another bug was introduced, see my screenshot
,
Aug 2 2014
Please look how are rendered fonts on this website. Next screenshot from Firefox (Chrome 36 was the same. As you can see, chrome introduced very ugly font rendering if aliasing is disabled. Other browsers - no such issue. Unaceptable.
,
Aug 3 2014
emsoft1: This bug is about the UI font being too small. #165 and #166 are unrelated; please file a new bug to track that issue. Please also compile https://github.com/derat/font-config-info and paste the output from running "./font-config-info -f 'monospace 12px'" into the new bug. Feel free to add a link to the new bug here. I will disable comments on this bug soon.
,
Aug 3 2014
New issue here: https://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=399952
,
Aug 4 2014
I upgraded from Chrome 34 to Chrome 35 (and subsequently 36). After updating to 35, I noticed that the font used for the tabs and bookmarks, while legible, are a bit larger and not as antialiased as I'm used to seeing. Am I experiencing the bug discussed here? Or am I seeing a different issue? I can't get font-config-info to compile on my Fedora 18 machine. $ xrdb -q | grep -i Xft Xft.antialias: 1 Xft.dpi: 96 Xft.hinting: 1 Xft.hintstyle: hintfull Xft.rgba: none $ cat ~/.fonts.conf <?xml version='1.0'?> <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <match target="font"> <edit mode="assign" name="rgba"><const>rgb</const></edit> <edit mode="assign" name="autohint"><bool>true</bool></edit> <edit mode="assign" name="hinting"><bool>true</bool></edit> <edit mode="assign" name="hintstyle"><const>hintfull</const></edit> <edit mode="assign" name="antialias"><bool>true</bool></edit> <edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit> </match> </fontconfig> Thanks,
,
Aug 4 2014
gitman: It may be related. Please check if the problem is still there in Chrome 38. If so, please file a new issue with before/after screenshots.
,
Oct 21 2014
Fedora 20 with Chrome 38. Fonts are too large for the bookmark bar.
,
Oct 21 2014
I should add--resolution is 3200x1800. 38 looks fine on 1920x1080.
,
Oct 21 2014
Debian Sid, 1920x1080, all ok.
,
Oct 21 2014
theoriginalbrianmiller@: This bug is about fonts being too small and has already been marked fixed. Please file a new bug and include before/after screenshots and the output from running https://github.com/derat/font-config-info and paste its ID here.
,
Dec 10 2014
Hi people I am having the same problem but in chrome canary. could some one please help i really don't want to make another user. I have re-installed 41.0.2244.0 canary and still happens. I made a short video
,
Dec 10 2014
kwedmid: This was a Linux issue. It looks like you're using Windows. Please file a new bug at http://crbug.com/new. |
|||||||||||||||
| ► Sign in to add a comment | |||||||||||||||
16.3 KB View Download