[Pkg-chromium-maint] Bug#763421: Bug#763421: fixed in chromium-browser 43.0.2357.65-1
bernat at debian.org
Thu May 21 20:03:54 UTC 2015
❦ 21 mai 2015 21:36 +0200, Yves-Alexis Perez <corsac at debian.org> :
>> Well, I have no more idea. I am using 144 DPI (set through XSETTINGS and
>> through the X server via xrandr) and Chromium correctly handles this
>> since this version
> Maybe there's a cutoff somewhere, I'm not sure. I've tried to force 144
> dpi but it still doesn't look good with the default scaling (but it's
> not as bad, and I know I like my widgets tinier than most people).
There may be some restrictions on the factor you can set. For example,
GDK had a long time limitation of only allowing integers (GDK_SCALE
needs to be an integer as far as I know). Maybe there is still some
restrictions. 144 is 1.5*96. You can try 192 too to see if the result is
I can give you a screenshot of what I have to compare, but the text on
the tabs should be of the same size as the text in the omnibar (unlike
your very first screenshot).
>> (through switching from HiDPI to regular DPI leaves
>> blurry fonts, but that's minor).
> What “switching from HiDPI to regular DPI” means, here?
Switching to an external screen for example. GTK apps are able to adapt
automatically. And now Chromium too, but the fonts become a bit
blurry. Stop/start Chromium fixes that.
>> Just in case, with dump_xsettings, no settings that could influence
> Here's the complete dump:
Nothing suspicious here.
Don't sacrifice clarity for small gains in "efficiency".
- The Elements of Programming Style (Kernighan & Plauger)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 818 bytes
Desc: not available
More information about the Pkg-chromium-maint