New issue
Advanced search Search tips

Issue 810794 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Max window have 2px black border in left

Reported by vhp...@msn.com, Feb 9 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36

Steps to reproduce the problem:
See attached image please.

What is the expected behavior?
*

What went wrong?
*

Did this work before? N/A 

Chrome version: 64.0.3282.140  Channel: stable
OS Version: 10.0
Flash Version: 

*
 
QQ截图20180210012359.png
15.7 KB View Download
Labels: Needs-Triage-M64
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on chrome reported version 64.0.3282.140 using windows 10 with steps mentioned below
1) Launch chrome reported version and maximized the screen
2) Screen get maximized with out any black border on the left side

@Reporter:
Please find the attached screen shot for your reference and let us know if we missed anything in reproducing the issue, try to reproduce the issue by creating new person and let us know if the issue still persists.

Thanks!
810794.PNG
44.2 KB View Download

Comment 3 by vhp...@msn.com, Feb 13 2018

Sorry, I found that the problem was caused by QQ. And I've already fed back to the QQ team. But it's weird that it only seems to affect Chrome, and no other software is affected.
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 13 2018

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "viswa.karala@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
Status: WontFix (was: Unconfirmed)
As per comment#3, as this issue is not specific to chrome, hence closing this issue.

@Reporter:
Feel free to raise a new issue if it is reproducible and specific to chrome.

Thanks!

Sign in to add a comment