New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667133 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Sep 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

URL auto complete and status bar off by 1 pixel on 150% DPI on Windows

Reported by goo...@johnkoerner.net, Nov 20 2016

Issue description

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

Steps to reproduce the problem:
1. Configure Windows to use 150% in the Customize your display dialog in Windows 10.
2. Start typing in the URL
3. Notice that the auto complete UI appears 1 pixel too far to the left.

What is the expected behavior?
The status bar and URL auto complete stay within the window.

What went wrong?
The UI is off by 1 pixel.  On multi-monitor displays, when Chrome is maximized, these pixels are displayed on other monitors. 

Did this work before? N/A 

Chrome version: 54.0.2840.99  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

Similar to issue https://bugs.chromium.org/p/chromium/issues/detail?id=435910

Tested on Windows 10 with 3 displays.
 - Left Display 1920x1080 - 100% DPI
 - Center Display 3840x2160 - 150% DPI
 - Right Display 1280x1024 - 100% DPI
 
AutocompleteOffBy1Pixel.png
48.3 KB View Download
StatusBarOffBy1Pixel.png
27.6 KB View Download
Labels: Needs-Triage-M54
Labels: M-54
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 10(dual monitor) using chrome reported version #54.0.2840.99, latest dev #56.0.2924.4 and latest canary #57.0.2929.0.

Attached a screen cast for your reference.

Following are the steps followed to reproduce the issue.
------------
1. Configured Windows 10(2 monitors) to use 150% in the Customize your display dialog in Windows 10.
2. Started typing in the URL.
3. Observed that the URL auto complete stayed within the window as expected.

Reporter@ - Could you please check this issue on latest canary #57.0.2929.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
667133.mp4
2.5 MB View Download
I was able to repro it on canary #57.0.2928.0 (That is what I was able to download).

I think a factor may be different resolutions/DPI per monitor.  See the attached video.
Chrome1PixelBug.mp4
886 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 30 2016

Labels: -Needs-Feedback Needs-Review
Owner: krajshree@chromium.org
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sureshkumari@chromium.org
Labels: -Needs-Review Needs-Feedback
Owner: ----
Unable to reproduce the issue on Windows 10(dual monitor) using chrome stable version 55.0.2883.75 and latest canary 57.0.2938.0 with steps mentioned above with different screen resolutions.

Reporter@ could you please upgrade to latest chrome version and please let us know if the issue still persists.

Thanks.. 

Canary Version 57.0.2943.0 canary (64-bit) still exhibits this behavior.
Project Member

Comment 8 by sheriffbot@chromium.org, Dec 14 2016

Labels: -Needs-Feedback Needs-Review
Owner: sureshkumari@chromium.org
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Feedback
Owner: ----
Unable to reproduce the issue on windows-10 (dual monitor) using chrome stable version 55.0.2883.87 and latest canary 57.0.2963.0.

Reporter@ could you please check the issue in latest chrome version and let us know your observations if the issue still persists.

Thanks.
Canary 57.0.2966.0 still exhibits this behavior.

I have reproduced on multiple Windows 10 machines.  I think one key is that one monitor has a DPI scaling greater than 100%, while the other monitor has the default DPI scaling.
Project Member

Comment 11 by sheriffbot@chromium.org, Jan 6 2017

Labels: -Needs-Feedback Needs-Review
Owner: sureshkumari@chromium.org
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919 
Labels: -Needs-Review
I was able to repro it on stable #61.0.3163.91.

Info: 
Windows Version 10.0.15063
GPU Intel Graphics 5500, driver 20.19.15.4549 (2016-11-10)

Following are the steps followed to reproduce the issue.
------------
1. Configured Windows with 2 monitors, main using 100% dpi and external using 125% dpi
2. Started typing in the URL in the second URL.
3. Observed that one pixel from the URL auto complete leaks to the main monitor (image attached)
4. Observed GPU artifacts and lag (delay) on rendering in the external monitor.
5. Observed that the issue does not reproduce when the two displays use the same dpi.
------------

bug.png
31.4 KB View Download
Cc: -sureshkumari@chromium.org kkaluri@chromium.org
Components: UI>HighDPI
Labels: hasbisect-per-revision
Owner: robliao@chromium.org
Status: Assigned (was: Unconfirmed)
Tested this issue on Windows 10 with chrome Stable #61.0.3163.100, Canary #63.0.3222.0
On 150% DPI on windows observed a 1 pixel black border around the window.
Considering this as bad behavior of this issue, executed the per-revision bisect script.

Issue has broken in M54.

Bisect Info:
===========
Good build :  54.0.2807.0,  Revision Range - 407480
Bad build  :  54.0.2808.0,  Revision Range - 407658

After executing the per-revision bisect script, i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/96b9ba41a7be9329fd486b973082a068bf7ec07c..23364eecc5d1bb1770f8c22a7c0a320154e3eac7

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/23364eecc5d1bb1770f8c22a7c0a320154e3eac7

robliao@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.


667133-Good.PNG
237 KB View Download
667133-Bad.PNG
123 KB View Download
An workarround for this issue is to set 'Omnibox UI Narrow Dropdown' to enabled in chrome://flags/ . This mitigated the issue in 63.0.3223.1 (Official Build) canary SyzyASan (32-bit) .
Status: Archived (was: Assigned)
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!

Sign in to add a comment