New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 23 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

UI (tabs, favs, search bar, ...) takes way too much space on Chrome 43 Beta Linux

Reported by misterma...@gmail.com, Apr 16 2015

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.18 Safari/537.36

Steps to reproduce the problem:
1. Have a 13.3 inches laptop with 1080p (169 dpi) with Linux
2. Open Chrome 43 Beta on Linux

What is the expected behavior?
I should be able to choose whether or not I want the 2x scaling to be enabled, or better yet be able to change the scaling factor I want including integers (in this case 1x scaling would be way enough for me).

What went wrong?
2x scaling is enabled by default with no way to change it in the settings (except for using force-device-scaling via command line at every launch), but very inconvenient. 2x scaling is way too big for a laptop this size with this resolution, it's basically unusable like this. The web-content scales nicely, but the UI elements take way too much space.

I understand it happens because of the work currently being done for Chrome HiDPI on Linux but until it is easily configurable by the user, either by using the system-wide scaling value the user chose (like Opera does) or by choosing a scaling value inside the browser itself (not possible right now as far as I know), HiDPI shouldn't ship by default, in my case it makes Chrome simply unusable.

Did this work before? Yes It "worked" on Chrome 42, because HiDPI support on Linux wasn't shipping yet

Chrome version: 43.0.2357.18  Channel: beta
OS Version: Ubuntu 14.10
Flash Version: Shockwave Flash 17.0 r0

I do want to point out that I'm extremely thankful for the work being done on HiDPI support on Linux, I just don't think it's ready just yet.
 
Capture du 2015-04-16 21:06:58.png
229 KB View Download

Comment 1 by deni...@gmail.com, Apr 17 2015

I'm also seeing this problem with Chrome 43.0.2357.18 beta (64-bit) on Fedora 21 running GNOME 3.

To restore the Chrome 42 behaviour on Linux until this is fixed, the command line flag to use is "--force-device-scale-factor=1"

Comment 2 by m...@zumstrull.net, Apr 17 2015

Also happens on a 1920x1080 Thinkpad T440s. It's true that this display is somewhat high res, but it's not retina grade and 2X scaling looks cartoonish.
A quick "fix" I'm using right now is including the "--force-device-scale-factor=1" in the google-chrome-beta.desktop file, so I don't have to use the command line for each launch.

To edit the .desktop, launch "sudo gedit /usr/share/applications/google-chrome-beta.desktop" (without quotes, and with the text editor of your choice if it's not gedit) in the terminal, and find the "Exec=/usr/bin/google-chrome-beta %U
" line and change it to be "Exec=/usr/bin/google-chrome-beta --force-device-scale-factor=1 %U". 

It's worth noting that integer scaling seems to work as well, if 2x is too big but 1x is too small.

It's more a temporary fix than anything, but it gets the job done more conveniently than by launching chrome through the terminal each time.

Hope that helps other people in this situation.

Comment 4 by sadrul@chromium.org, Apr 19 2015

Cc: sadrul@chromium.org stapelberg@google.com
Status: Available

Comment 5 by rabb...@gmail.com, Apr 20 2015

Same on Version 43.0.2357.18 beta (64-bit), on Ubuntu 14.04 on Thinkpad Carbon x2 with resolution scaled down to 1920/1080.
https://codereview.chromium.org/1078423002/ is allowing arbitrary scale factors, i.e. chrome will also use something like 1.5x if that more closely matches what your setup tells chrome to use.

I think this addresses the concern brought up here. If not, please correct me.
Owner: stapelberg@google.com
I don't know if the patch you mentionned has already been merged, but the latest beta (43.0.2357.37) doesn't seem to have fixed the issue. 2x scaling seems to be the default still on my laptop, and as far as I know there is still no straightforward way to affect that default, the only option is to use the "--force-device-scale-factor=1" command line flag.
The patch is still under review, I’m having trouble fixing the failing tests.

Comment 10 by busho...@gmail.com, Apr 24 2015

I'm seeing the same issue.  Attached two screenshots.  One of chrome stable 42, one of beta 43.  Both are full screen, 100% zoom, medium font, 2560x1440 on an 11" screen.
chrome-highdpi-beta43.png
1.3 MB View Download
chrome-highdpi-stable42.png
423 KB View Download
Project Member

Comment 11 by bugdroid1@chromium.org, Apr 24 2015

------------------------------------------------------------------
r294979 | stapelberg@google.com | 2015-04-24T14:26:08.346364Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/tools/build/scripts/slave/xvfb.py?r1=294979&r2=294978&pathrev=294979

xvfb: set dpi to 96 (xvfb defaults to 100).

Tests assume that the DPI is effectively 96. Up until recently, this was
the case because chromium only supported 100% (corresponding to 96 dpi)
or 200% (corresponding to 192 dpi) scaling in its UI.

With https://codereview.chromium.org/1078423002/, we want to change that
to better reflect the hardware that many people have today. Applying
that CL without also changing the DPI results in tests failing because
of off-by-a-few-pixel errors.

BUG= 477716 , 143619 

Review URL: https://codereview.chromium.org/1105903002
-----------------------------------------------------------------

Comment 12 by mmoss@chromium.org, Apr 24 2015

 Issue 480898  has been merged into this issue.
Project Member

Comment 14 by bugdroid1@chromium.org, Apr 28 2015

Labels: merge-merged-2357
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7cec497feff0d8fa0de1fc59271a29f3a0f3f043

commit 7cec497feff0d8fa0de1fc59271a29f3a0f3f043
Author: Magnus Jedvert <magjed@google.com>
Date: Tue Apr 28 11:42:03 2015

Allow arbitrary scale factors.

As discussed in https://codereview.chromium.org/1070433002/, this CL
allows arbitrary scale factors, which works because chromium uses the
resource most closely matching the scale factor (e.g. 1x for 1.25x,
but 2x for 1.9x) and scales it.

BUG= 143619 , 477716 

Review URL: https://codereview.chromium.org/1078423002

Cr-Commit-Position: refs/heads/master@{#326851}
(cherry picked from commit b3ca230ddd7d1238ee96ed26ea23e369f10dd655)

device scale factor detection: use gtk-xft-dpi consistently

Before this CL, we used either gtk-xft-dpi (UI fonts) or the physical DPI of
a more or less random display. This CL consistently uses gtk-xft-dpi which
is the better alternative: users can directly influence it (by changing the
Xft.dpi X resource, or via their gtkrc).

See also https://github.com/derat/font-config-info for displaying your
current system settings.

This is a re-do of https://codereview.chromium.org/1070433002/, but with
https://codereview.chromium.org/1084453002/ applied (fixes content_shell).

BUG= 473089 ,  143619 

Review URL: https://codereview.chromium.org/1085603002

Cr-Commit-Position: refs/heads/master@{#324928}
(cherry picked from commit d459a5c49a02507b9ac77ffbbf33dffeb3bc9c34)

R=stapelberg@google.com
TBR=erg, estade, oshima

Review URL: https://codereview.chromium.org/1103383004

Cr-Commit-Position: refs/branch-heads/2357@{#246}
Cr-Branched-From: 59d4494849b405682265ed5d3f5164573b9a939b-refs/heads/master@{#323860}

[modify] http://crrev.com/7cec497feff0d8fa0de1fc59271a29f3a0f3f043/chrome/browser/ui/libgtk2ui/gtk2_ui.cc
[modify] http://crrev.com/7cec497feff0d8fa0de1fc59271a29f3a0f3f043/chrome/browser/ui/libgtk2ui/gtk2_ui.h
[modify] http://crrev.com/7cec497feff0d8fa0de1fc59271a29f3a0f3f043/testing/xvfb.py
[modify] http://crrev.com/7cec497feff0d8fa0de1fc59271a29f3a0f3f043/ui/views/linux_ui/linux_ui.h
[modify] http://crrev.com/7cec497feff0d8fa0de1fc59271a29f3a0f3f043/ui/views/widget/desktop_aura/desktop_screen_x11.cc

Project Member

Comment 15 by bugdroid1@chromium.org, Apr 28 2015

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/bling/chromium.git/+/7cec497feff0d8fa0de1fc59271a29f3a0f3f043

commit 7cec497feff0d8fa0de1fc59271a29f3a0f3f043
Author: Magnus Jedvert <magjed@google.com>
Date: Tue Apr 28 11:42:03 2015

Comment 16 by Deleted ...@, May 20 2015

I'm sorry, but HiDPI-scaling in the new stable version (43.0.2357.65 (64-bit)) is still clearly flawed. I'm running on a 109 DPI display (2560x1440, 27"), and the HiDPI-scaling is outright ugly. Everything is blurry, both graphics and text.

In some cases you can 'fix' this. Choosing a different tab and revisiting the original one will make the entire page a bit crisper. But it doesn't work all the time, and it's a lousy solution anyway. A clearly visible bug like this one should never end up in a stable branch.

The attached image shows the top part of a website. First the 'original' look, second is the revisited tab, and third is how it's supposed to look without HiDPI-scaling.
Screenshots.png
1.3 MB View Download
arumesgm, this problem affects only certain hardware environments (hence it wasn’t discovered earlier) and has been fixed in git already AIUI. See https://code.google.com/p/chromium/issues/detail?id=484400 and https://code.google.com/p/chromium/issues/detail?id=485183
Even after update to 43.0.2357.81, I still have this problem.

Thinkpad T510, 118x118 dots per inch.
Not sure what you refer to with “this problem”. If it’s comment #16, see  issue #484400  — the summary is that the dev channel (44.0.2403.9 or newer) has the fix.
I mean "UI takes way too much space". But the bug described in #16 also affect me, thanks, I'll try dev version.
big-ui.png
187 KB View Download
Project Member

Comment 21 by bugdroid1@chromium.org, May 26 2015

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

commit 1e83acd552618ab337d286187ed23d84434bd122
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Tue May 26 20:46:41 2015

Revert "Allow arbitrary scale factors."

Reason for revert: crbug.ccom/484400

BUG= 143619 , 484400 
TBR=erg@chromium.org, estade@chromium.org, oshima@chromium.org, stapelberg@google.com

> Allow arbitrary scale factors.
>
>    As discussed in https://codereview.chromium.org/1070433002/, this CL
>    allows arbitrary scale factors, which works because chromium uses the
>    resource most closely matching the scale factor (e.g. 1x for 1.25x,
>    but 2x for 1.9x) and scales it.
>
>    BUG= 143619 , 477716 
>
>    Review URL: https://codereview.chromium.org/1078423002
>
>    Cr-Commit-Position: refs/heads/master@{#326851}
>    (cherry picked from commit b3ca230ddd7d1238ee96ed26ea23e369f10dd655)
>
>    device scale factor detection: use gtk-xft-dpi consistently
>
>    Before this CL, we used either gtk-xft-dpi (UI fonts) or the physical DPI of
>    a more or less random display. This CL consistently uses gtk-xft-dpi which
>    is the better alternative: users can directly influence it (by changing the
>    Xft.dpi X resource, or via their gtkrc).
>
>    See also https://github.com/derat/font-config-info for displaying your
>    current system settings.
>
>    This is a re-do of https://codereview.chromium.org/1070433002/, but with
>    https://codereview.chromium.org/1084453002/ applied (fixes content_shell).
>
>    BUG= 473089 ,  143619 
>
>    Review URL: https://codereview.chromium.org/1085603002
>
>    Cr-Commit-Position: refs/heads/master@{#324928}
>    (cherry picked from commit d459a5c49a02507b9ac77ffbbf33dffeb3bc9c34)
>
>    R=stapelberg@google.com
>    TBR=erg, estade, oshima
>
>    Review URL: https://codereview.chromium.org/1103383004
>
>    Cr-Commit-Position: refs/branch-heads/2357@{#246}
>    Cr-Branched-From: 59d4494849b405682265ed5d3f5164573b9a939b-refs/heads/master@{#323860}

Review URL: https://codereview.chromium.org/1159703005

Cr-Commit-Position: refs/branch-heads/2357@{#440}
Cr-Branched-From: 59d4494849b405682265ed5d3f5164573b9a939b-refs/heads/master@{#323860}

[modify] http://crrev.com/1e83acd552618ab337d286187ed23d84434bd122/chrome/browser/ui/libgtk2ui/gtk2_ui.cc
[modify] http://crrev.com/1e83acd552618ab337d286187ed23d84434bd122/chrome/browser/ui/libgtk2ui/gtk2_ui.h
[modify] http://crrev.com/1e83acd552618ab337d286187ed23d84434bd122/testing/xvfb.py
[modify] http://crrev.com/1e83acd552618ab337d286187ed23d84434bd122/ui/views/linux_ui/linux_ui.h
[modify] http://crrev.com/1e83acd552618ab337d286187ed23d84434bd122/ui/views/widget/desktop_aura/desktop_screen_x11.cc

Can't see any problems with 45.0.2414.0. Thanks for the help and your work!

Comment 23 by Deleted ...@, Jun 10 2015

Running Chrome Version 43.0.2357.124 (64-bit) on Ubuntu 14.04.

Screen resolution is 1920x1080 on a Dell XPS 13

I am seeing the DPI scale factor get "doubled" and things are huge and blurry.

If I run it with this command line, it fixes it (but I don't want to have to do that everytime):

~$ google-chrome --force-device-scale-factor=1


#23: you’re posting to the wrong bug. 498426 is tracking the problem you’re seeing.

Sign in to add a comment