Issue metadata
Sign in to add a comment
|
Display settings : UI dropdown for display setting claims that 4K display resolution is 3840 x 2160, while in actuality is using 1920 x 1080 2X |
||||||||||||||||||||||||
Issue description<b>Chrome Version: <From about:version: Google Chrome x.x.x.x></b> <b>Chrome OS Version: <From about:version: Platform x.x.x.x></b> Chrome OS Platform: Kevin, Snappy <b>Network info: <network, encryption type, router model (if known)></b> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Plug in Kevin to LG oled55e6p (or similar) monitor (2) Go to chrome settings fro display. (3) Check the display dropdown for external display, compare it to UI scaling by visual inspection Expected Result: 1920 x 1080 2X, consistent with visual inspection of rendering of UI. Actual Result: Says 3840 x 2160 instead of 1920 x 1080 2X How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? Workaround is to switch to 1920 x 1080 2X in the dropdown (which will have no effect), then switch back to 3840 x 2160. Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=57951384961
,
Apr 19 2017
That's not quite the issue here. Steps to reproduce: 1. Plug in 4K display. Visually, mode is 1080pX2. 2. Go into display UI. Selection shows 3840x2160. 3. Change resolution to 1080pX2 in UI. Nothing changes, because you were actually in that mode already. 4. Change resolution back to 3840x2160 in UI. Now scaling has changed to 1X. So the issue is that the display settings UI is not reporting the correct mode upon first connect.
,
Apr 19 2017
Ah ok. Then it's a UI problem and should go to UI folks...
,
Apr 19 2017
You are on M57, correct?
,
Apr 19 2017
Version 58.0.3029.76 beta (64-bit) Platform 9334.50.0 (Official Build) beta-channel caroline ARC Version 3912574 Firmware Google_Caroline.7820.286.0
,
Apr 19 2017
afakhry: David's feedback report above is from 58 as well : CHROME VERSION 58.0.3029.51 beta CHROMEOS_AUSERVER <URL: 1> CHROMEOS_RELEASE_BOARD kevin-signed-mpkeys CHROMEOS_RELEASE_DESCRIPTION 9334.33.0 (Official Build) beta-channel kevin CHROMEOS_RELEASE_TRACK beta-channel CHROMEOS_RELEASE_VERSION 9334.33.0
,
Apr 19 2017
,
Apr 19 2017
M57 and M58 both has this problem. This issue was fixed recently in M59 in issue 701389 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by marc...@chromium.org
, Apr 19 2017