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

[Yves-Alexis Perez]

On jeu., 2015-05-21 at 22:03 +0200, Vincent Bernat wrote:
>  ❦ 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
> better.

Nop still the same.
> 
> 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).

Well, in my case, I'm just fine with no scaling factor (=1). Not sure
what's usually applied to HiDPI settings versus regular.
> 
> >>  (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.

Plugging an external screen and moving Chromium window to it doesn't
change either.

Regards,
-- 
Yves-Alexis
-------------- 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/9d0a36a9/attachment.sig>