Issue metadata
Sign in to add a comment
|
Going full screen on second monitor creates border on top and left
Reported by
sam.w.ne...@gmail.com,
Jun 23 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Put chrome browser on second screen 2. Hit F11 to go full screen What is the expected behavior? If you do this on the main monitor it properly fills the entire display What went wrong? The browser did not fill the entire display, it left a thick transparent border on the top and left. Did this work before? N/A Chrome version: 58.0.3029.110 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: - I have a dark theme applied - Both monitors are the same 1080p Dell monitors
,
Jun 27 2017
Unable to reproduce this issue on Windows 10 with chrome #58.0.3029.110, #59.0.3071.115 with dual monitors (dell-2407WFP), observed a chrome is displaying full on monitor #2. Attaching a screencast for reference. sam.w.nesbitt@ could you please look into it and let us know your observations and also confirm whether this issue is similar to issue 730163 or not ? Thank You....
,
Jun 27 2017
It seems to only happen when video playback is running on the 2nd monitor. Please see https://bugs.chromium.org/p/chromium/issues/detail?id=631020 Thanks.
,
Jun 27 2017
This is a different issue than 730163. I did some additional testing and it only happens if the window is maximized and then I go full screen. This happens even with only one tab opened in the default new tab page so I do not think it is related to 631020.
,
Jun 27 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 27 2017
I don't think I have a way of easily recording my screen so I used the problem step recorder which is built into windows and gives some snapshots of my test.
,
Jun 28 2017
Still we are unable to reproduce the issue as per comment#4 & #6 on Windows 10 Dual monitor (Dell -both are having same resolution) using chrome reported version#58.0.3029.110,Stable#59.0.3071.115 & Canary#61.0.3142.3. No border space observed at the top left corner after full screen on both main monitor and second monitor also. Please find the attached screencast for reference. Could some one from MTV team please look into this issue as we(chrome-hyd team) do not have Windows 7 Dual monitor with above specifications.Adding 'TE-NeedsTriageFromMTV' label for further investigation.
,
Jun 28 2017
Is there anything you would like me to do to troubleshoot this for you guys? I have a technical background so don't be scared to lay it on me.
,
Jun 29 2017
This looks very much like an issue I see constantly, but I have one landscape and one portrait monitor. The reproduction steps for Windows 7: - Start chrome. - Maximise a window to a screen. - Change the theme to Windows Basic. (It's simplest to start a program that has the compatibility checkbox "disable desktop composition" checked.) - Press F11 to go fullscreen. (Or use an alternative method, such as maximising a YouTube video). What I have in common with the original post is that this only happens when the theme is changed. It won't happen on the default theme. This seems to be the key.
,
Aug 1 2017
Team, please re-triage further.
,
Oct 17 2017
sam.w.nesbitt@ are you still seeing the same in latest stable?
,
Oct 18 2017
Able to reproduce this issue by the steps mentioned in comment #9 on Windows 7 with Chrome Stable 62.0.3202.62 and Canary 64.0.3242.0. Unable to reproduce this issue on Ubuntu 14.04 and Windows 10 and issue is not applicable on Mac OS. Below is the Bisect Information. Bisect Information: ===================== Good Build 52.0.2706.0 Revision-386523 Bad Build 52.0.2707.0 Revision-386876 Unable to find the changelog using the old bisect script as all good builds are triggered. Hence below is the changelog from omahaproxy. CHANGELOG URL: =============== https://chromium.googlesource.com/chromium/src/+log/52.0.2706.0..52.0.2707.0?pretty=fuller&n=10000 From the above Changelog, the possible suspect is Review URL: ============ https://codereview.chromium.org/1859283003 As jbauman@ is not on Chrome anymore, requesting Reviewer sky@ to please check this issue and help us in assigning it to the right owner. Thanks.!
,
Oct 18 2017
I just retested this and it is still an issue. Version 61.0.3163.100
,
Oct 20 2017
,
Oct 20 2017
I'm not a good owner for this. Allen, any chance you can take a look? Worse case, we should revert.
,
Jan 18 2018
Issue 670435 has been merged into this issue.
,
Feb 23 2018
I wonder if this is related to https://crbug.com/806936 ?
,
Mar 29 2018
Issue 818598 has been merged into this issue.
,
Apr 25 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Jun 23 2017Labels: Needs-Bisect Needs-Triage-M61