Issue metadata
Sign in to add a comment
|
at 175% system scaling, when window is not maximized, tabs are not connected to tab bar
Reported by
billdill...@gmail.com,
Sep 8 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36 Steps to reproduce the problem: Windows 10 version 1703, 175% scaling, when a Chrome window is not maximized, the tabs are not connected to the bar, there is a 1 pixel gap. What is the expected behavior? What went wrong? I've included screenshots of normal chrome as well as an incognito window because the 1 pixel gap is clearer to see with incognito windows. (I colored the gap red in the normal chrome window screenshot) Also, perhaps this is not just a Windows 10 issue, could someone else check linux/macOS/Chrome OS Did this work before? N/A Chrome version: 61.0.3163.79 Channel: stable OS Version: 10.0 Flash Version:
,
Sep 11 2017
,
Sep 13 2017
I should add, this issue is visible any time a Chrome window is split screen
,
Sep 15 2017
billdillensrevenge@ thanks for the issue. Unable to reproduce this issue on Windows 7,10, Mac OS 10.12.6 and Ubuntu 14.04 using the latest stable 61.0.3163.91 and Canary 63.0.3215.0 with the below steps. 1. Launched Chrome and opened a incognito window. 2. Opened few tabs and zoom in the page to 175%. 3. Could observe no gap on the tab stripe. Please find the attached screen shot for reference. Request you to retry the issue on a new Chrome profile without any flags/extensions and update the thread if the issue still exists. Thanks..
,
Sep 15 2017
Not zooming in the webpage to 175%, set the Windows 10 system scaling to 175%. I don't think macOS labels their scalings as percents so you'll have to do a little bit of math to figure out which resolution is 175% on whichever mac is available to you
,
Sep 15 2017
Thank you for providing more feedback. Adding requester "susanjuniab@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
,
Sep 19 2017
Tested on latest Chrome Stable #61.0.3163.91, Canary # 63.0.3219.0 on Windows 10 and able to reproduce the issue. Using the per-revision bisect providing the bisect results, Good build: 53.0.2753.0 (396745) Bad build: 53.0.2754.0 (397000) You are probably looking for a change made after 396928 (known good), but no later than 396940 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/dc439ca55463132360e971e82a878e5e57b99dcc..028a16f9d437a8738798c44ab91b408f2df07263 https://chromium.googlesource.com/chromium/src/+/bacee65d8140989fdb60dc59b5c3ddfaf1a332c9 From the CL above, assigning the issue to the owner concerned. @robliao: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned. Review-URL: https://codereview.chromium.org/2012083002 Issue is not observed on Mac 10.12.6 and Ubuntu 14.04. Thanks.
,
Nov 26 2017
enabling pixel canvas fixes this issue (--enable-pixel-canvas-recording)
,
Dec 14 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by billdill...@gmail.com
, Sep 8 201777.0 KB
77.0 KB View Download