[Pkg-chromium-maint] Bug#763421: Bug#763421: fixed in chromium-browser 43.0.2357.65-1

Yves-Alexis Perez corsac at debian.org
Thu May 21 20:56:02 UTC 2015

On jeu., 2015-05-21 at 22:22 +0200, Vincent Bernat wrote:
>  ❦ 21 mai 2015 22:03 +0200, Vincent Bernat <bernat 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
> > better.
> If you wanted to dig a bit, the code is here:
>  http://sources.debian.net/src/chromium-browser/43.0.2357.65-1/chrome/browser/ui/libgtk2ui/gtk2_ui.cc/#L384-L392
> It seems there is almost no rounding. GetDeviceScaleFactor is then used
> for web rendering too. You could try to check what you get with


> Compile with gcc $(pkg-config --cflags --libs gtk+-3.0) -Wall dpi.c -o dpi

I think GTK+ has no issue using the DPI value, since other apps (whether
GTK2 like Xfce stuff, or GTK3 like zenity or others) have the correct
widgets and font size.
> Do you get the right value?

corsac at scapa: ./dpi
DPI: 179200

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20150521/afba5569/attachment.sig>

More information about the Pkg-chromium-maint mailing list