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

Issue 600280 link

Starred by 1 user
Status: WontFix
Owner:
█ nainar@chromium.org
Not on Chrome anymore
Closed: Apr 2016
Cc:
nyerramilli@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Highlight on radio button appears to be misaligned for 'Lynonym' extension.

Reported by adha...@etouch.net, Apr 4 2016 
Chrome Version:Chrome version:51.0.2699.0 (Official Build)ced319c78e3f9acc95394d81cc6763ed9a9e8371-refs/heads/master@{#384828}(32/64-bit)
OS:All(Aero enabled)

URL:https://chrome.google.com/webstore/detail/lynonym/mlaomkbolndecpefenllmdlgbmoooopk/related?hl=en

What steps will reproduce the problem?
(1)Launch chrome,navigate to above url and click on 'Add to Chrome'.
(2)Click on extension icon, in Extensions overlay and observe the highlighted radio button.

Actual:Highlight on radio button appears to be misaligned.
Expected:Highlight on radio button should appear properly.

This is a Regression issue broken in M-48, below is the Narrow bisect information:
https://chromium.googlesource.com/chromium/src/+log/a672c889ad8c0d6fc379019e57791fe98a7088c5..405a1676fea008a94841d25a21ec1c13e156a831?pretty=fuller&n=100  

Suspecting:r357306?

Good build:48.0.2552.0
Bad build:48.0.2553.0

Please help to reassign if your change is not the cause for this issue.
Actual.png
200 KB View Download
Expected.png
257 KB View Download

Comment 1 by kojii@chromium.org, Apr 6 2016

Cc: -nainar@chromium.org
Owner: nainar@chromium.org
nainar@, this looks like because of the rounding border in crrev.com/357305.

The radio button in question is
<label for="option1"><span><span></span></span>
and applies the following style:
border: 0.0625em solid rgb(192,192,192);

Can you have a look?

Comment 2 by nainar@chromium.org, Apr 6 2016 

A minimum test case of this bug repros the same on Firefox and Chrome (the fix landed by the patch mentioned in C#1 was an interop fix). Seems like the fix will have to be made on the developer's end. Will reach out to the team at Lynonym to get them to fix.

Comment 3 by nainar@chromium.org, Apr 6 2016

Status: WontFix (was: Assigned)
►

Sign in to add a comment