Multi monitor DPI issues when window moved via Win+Shift+Left/Right
Reported by
shadow.g...@gmail.com,
Jul 25 2016
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2805.0 Safari/537.36 Steps to reproduce the problem: 1. Open browser on high-dpi (4k@200%) monitor 2. Press Win+Shift+Left/Right to move window to other (target) monitor with normal-dpi 1080p@100% What is the expected behavior? What went wrong? If window is Maximized: Window is rendered with negative vertical offset, top is cut, bottom have black strip. If window is not maximized - there are two different resulting behaviors: 1. if browser window width is less than target monitor resolution width (for example, window width is more then 1920px and target monitor is 1080p@100% (1920px): there will be a gap between window title/header (with control buttons) and browser back/forward controls with address bar which is not drawn and is seen as black bar on screenshot Canary_54.0.2805.0_Rev407311_notmaximized_1.png. It have height of title/header. 2. else (browser window width is more than target monitor resolution width): a) size of window is not persistent when window is moved between monitors, width will gradually increase with each move until it will reach technical maximum width Example set of window.outerWidth over each move between screens: 570(source), 1126(target), 563(source), 1622(target), 811(source), target(2118) b) Window scale is not identified correctly when window is moved from normal-dpi (1080p@100%) to high-dpi (4k@200%) monitor, though it will correct itself is window is resized in any direction OR moved See screenshot: Canary_54.0.2805.0_Rev407311_notmaximized_2.png Did this work before? N/A Chrome version: 54.0.2805.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 Setup: Dell P2415Q - 3840x2160@200% (source) Asus VH242H - 1920x1080@100% (target) Google Chrome 54.0.2805.0 (Official Build) canary (64-bit) Revision 1243666b4f5c7c48312233e1f6e6fda46191b184-refs/heads/master@{#407311} with --enable-per-monitor-dpi OS: Windows 10 Pro x64, not preview (stable) GPU: NVidia GTX 1080 stable driver 10.18.13.6839 from Jun 07, 2016, WHQL 368.39
,
Jul 26 2016
Probably related to issue #630748 ?
,
Aug 2 2016
On 54.0.2805.0, per-monitor DPI was default off. I don't observe this on my latest canary. See if this repros in the latest canary, where per-monitor DPI is on for Windows 10.
,
Aug 2 2016
I was and am using flag --enable-per-monitor-dpi , though, can't see any difference with or without it. Tested Canary 54.0.2816.4, visual results are the same. Chrome is listed as dpi aware.
,
Aug 12 2016
,
Feb 14 2017
I would say this is a CONFIRMED issue. See this very long thread with all folks reporting the same issue under the same circumstances. https://productforums.google.com/forum/#!topic/chrome/3C1YPjD7-Fg;context-place=starred
,
May 26 2017
Having the same issue when using a 4K laptop display @ 200% scaling and connecting an external 1080p @ 100% scaling.
,
Jun 8 2017
I have the same issues since the chrome 59 update... 4k monitor on a notebook (only the external monitor is active, so this is the primary one) the borders are always present, they don't go away with any window state (maximised, restored, normal, initial open, docked, undocked, whatever, ...)
,
Jun 9 2017
I've finally been able to reproduce some of the effects described here.
,
Sep 17 2017
This is a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=656730 I believe. And there are other duplicates still out there. This is a pretty bad UI bug and with more and more people now with more High DPI displays it's becoming more commonly reported.
,
Sep 18 2017
Well, this specific bug was more about scaling issues when window is moved across, and these problems are still there, 7 major versions into stable...
,
Sep 25
Archiving old bugs that have only received trivial updates for some time. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 26
This issue is still present and causes inconsistent experience due to behaviour different from what is expected |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by danakj@chromium.org
, Jul 25 2016