New issue
Advanced search Search tips

Issue 648798 link

Starred by 3 users
Status: Archived
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Transition of Window between HIDPI and standard DPI monitors does not rescale Chrome in a KDE / Qt environment

Reported by ru...@starset.net, Sep 20 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. Grab a laptop with a HIDPI display, such as the Thinkpad X1 Carbon with the HIDPI 14" 2560x1440 display
2. Setup KDE plasma-desktop 5.7.4 (currently in Debian Sid)
3. In KDE's System Settings > Display and Monitor, select the Scale Display option
4. Set the scaling to 1.5, ok and apply
5. Log out and back in to KDE
6. Install Chrome
7. Plug in a 2nd display that is a standard DPI, like a 27" Dell U2713HM running at 2560x1440
8. Open KDE terminal application, Konsole, on the laptop which is the first display
9. Do something to display some text, such as ls /
10. Drag terminal window to the 2nd display
11. Observe font getting resized and redrawn to accommodate the difference in DPI on the 2nd display
12. Open Chrome on the first display
13. Browser to a page with content
14. Move the browser window to the 2nd display
15. Observe
14. Drag Chrome window to the external 

What is the expected behavior?
Much like on OS X in a similar setup, Chrome rerenders its window down to a scaling factor of 1 to deal with the DPI difference and not look huge on the 2ndary display.

What went wrong?
Chrome remains scaled up by a factor of 1.5 regardless of the transition to the normal DPI display.

Did this work before? N/A 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: Debian Sid
Flash Version: 

I've honestly put in a request for a new HIDPI 4k 27" monitor because this issue is driving me up the wall.

Comment 1 by jrop...@gmail.com, May 1 2017 

I have been seeing this too, and I believe it is a regression, because it used to work.  For me it regressed last year sometime, but I don't know exactly when (I'm using Chromium on Ubuntu).

I don't use dual displays like the OP, but I do often switch between my laptop display, and an external display - I plug in the external display and operate the laptop in clamshell mode.  Chrome used to detect the change in scaling, and would update its scaling accordingly, now it doesn't, I have to restart Chrome if I want to detect the change in scaling.

I think a simplification of the title/description of this issue would be:

Chrome no longer detects changing scaling while running, it only detects the scaling on startup.

I've seen a lot of people try to answer this specific issue by telling people to use the force-device-scale-factor argument - but that is the wrong solution, that is only a solution when Chrome fails to detect the device scale factor on startup.  In this instance, Chrome is correctly detecting the scale factor on startup, but is not responding to any subsequent changes in scale factor.

Comment 2 by ru...@starset.net, May 1 2017 

So partially because of this bug and a bunch of other qt hidpi issues, I've picked up a 4K monitor and have gotten rid of my other monitors. I'm happy to test any fixes or work around but it might take me a few days to borrow another monitor from someone else in my office.
Project Member

Comment 3 by sheriffbot@chromium.org, May 1 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment