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

Issue 705388 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Use other robhogan account instead.
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression : Search engines text appears misaligned from RHS in chrome://md-settings/searchEngines.

Reported by rp...@etouch.net, Mar 27 2017

Issue description

Version: 59.0.3053.0 bba05f44fe583ffa69c22d36f91aaebe0ceea282-refs/heads/master@{#459685}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.11.6,10.12.1)

What steps will reproduce the problem?
1. Launch chrome, navigate to chrome://md-settings/searchEngines 
2. Now make any one default except Google,Bing,Yahoo search engines
3. Now observe RHS alignment of Google,Bing,Yahoo search engine list.(Refer screenshot)
 
Actual: Google,Bing,Yahoo search engine text in Manage search engines list appears misaligned from RHS
Expected: Google,Bing,Yahoo search engine text in search engine list appears misaligned from RHS

This is regression issue, broken in ‘M 59’ and will soon update other info :
Good build:59.0.3036.0
Bad build: 59.0.3037.0
 
Actual_screenshot.png
164 KB View Download
Expected_screenshot.png
163 KB View Download

Comment 1 by rp...@etouch.net, Mar 27 2017

Correction :
Expected : Google,Bing,Yahoo search engine text in Manage search engines list should appear properly aligned from RHS
Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: robhogan@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build:59.0.3036.0 (Revision:455621).
Bad build:59.0.3037.0 (Revision:455955).

You are probably looking for a change made after 455936 (known good), but no later than 455937 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/4af1264005620a483a209f4344c3782f62eee69a..246a46ddac2484d3860a4661010a683b0ab02289

From the CL above, assigning the issue to the concern owner

@robhogan : 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 concern owner.

Review-Url: https://codereview.chromium.org/2736003003
Note :Able to reproduce the issue in Win 10.0,Ubuntu 14.04 & Mac 10.12.3 and Able to reproduce in latest Canary #59.0.3053.0
Status: WontFix (was: Assigned)
There's no expectation for ellipsis to align on a particular side - it will always be placed at the first available character where the full ellipsis can fit on the line. This includes cases where the difference between the width of the ellipsis and the available width is less than a pixel, which I think is happening in at least one place here.

I think this is a wontfix.

Sign in to add a comment