Issue metadata
Sign in to add a comment
|
Regression : Letter 'O' appears bigger in font size for some search suggestions tool tip in chrome://settings page.
Reported by
rp...@etouch.net,
Nov 6 2017
|
||||||||||||||||||||||||
Issue descriptionVersion: 64.0.3260.0 (32/64-bit)eec83ceb16d47f70f5804a140687e268a6230b5c-refs/heads/master@{#514066} OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.1) What steps will reproduce the problem? 1. Launch chrome, navigate to chrome://settings/ and type 'O' in capital in 'Search settings' search box,observe 'O' in search suggestions tool tip Actual: Letter 'O' appears bigger in font size for some search suggestions tool tip on page(For Ex. Customize fonts) and also suggestions tool tip overlapping is seen (For Ex. Passwords and form section) Expected: Letter 'O' should appear in same font size in search suggestions tool tip throughout the page This is regression issue, broken in ‘M 63’ and will below is the bisect info : Good build: 63.0.3227.0 (Revision: 505232). Bad build: 63.0.3228.0 (Revision: 505449). You are probably looking for a change made after 505441 (known good), but no later than 505442 (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/239e5b8215692feaa750b3f2b1dcc8111349ddbb..c31a7fd20c45dd90838b9886302b87e58e6d3d16 From the CL above, assigning the issue to the concern owner @dschuyler- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Suspect : https://chromium.googlesource.com/chromium/src/+/c31a7fd20c45dd90838b9886302b87e58e6d3d16 Thanks!
,
Nov 10 2017
With response to comment #1 : Rechecked the above issue on Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.1) with latest canary chrome version : 64.0.3263.0 and the issue is still reproduced.Kindly refer the attached screen cast for your reference.
,
Nov 10 2017
After sync'ing to ToT I can repro it. Does that imply it's rather recent?
,
Nov 10 2017
@dschuyler: I suggest reverting locally the CL that was pointed out by the bisection (https://chromium.googlesource.com/chromium/src/+/c31a7fd20c45dd90838b9886302b87e58e6d3d16) to determine if the bisection was correct. If that's not the case, then performing build bisect from scratch could help figure out how recent this regression is.
,
Nov 10 2017
Sorry, I didn't mention that reverting the CL mentioned above didn't seem to help. I also meant to suggest that the prior code I was before sync ing didn't show the problem. That implies the bisect would be recent. I stopped looking at this because it's been bumped down to a pri-2. I'm happy to look at it further if needed (i.e. if the priority is higher than other issues).
,
Dec 21 2017
I verified that this is fixed by https://chromium-review.googlesource.com/c/chromium/src/+/830651. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dschuyler@chromium.org
, Nov 10 2017