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

Issue 668071 link

Starred by 1 user
Status: Duplicate
Merged: issue 675389
Owner:
█ dschuyler@chromium.org
Last visit > 30 days ago
Closed: Jan 2017
Cc:
█ anan...@chromium.org
█ meade@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
█ brajkumar@chromium.org
█ msrchandra@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Hand pointer is seen on hovering mouse pointer over white space beside 'Add address' and 'Add credit card' button.

Reported by lpa...@etouch.net, Nov 23 2016 
Chrome Version: 57.0.2929.0 (Official Build) d78075be67a3ee6520d1f8377cd69b478ebdf5ee-refs/heads/master@{#434071} 32/64 Bit.
OS: Windows (7,8,10), Mac (10.11.6, 10.12.1), Linux (14.04 LTS) 

Steps:
1. Launch chrome and navigate to chrome://md-settings/autofill
2. Hover the mouse pointer on the white space beside 'Add address' and 'Add credit card' button / try to click on that area.
3. Observe the mouse pointer.

Actual: Hand pointer is seen on hovering mouse pointer over white space beside 'Add address' and 'Add credit card' button which is not clickable.

Expected: Arrow pointer should be seen on hovering mouse pointer over white space beside 'Add address' and 'Add credit card' button.

This is a regression issue broken in M-55, will soon update the other info.

Manual Regression Range:
Good Build: 54.0.2840.68 
Bad Build: 55.0.2841.0
Actual_pointer.mp4
157 KB View Download
Expected_pointer.mp4
146 KB View Download

Comment 1 by rbasuvula@chromium.org, Nov 23 2016

Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: meade@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 54.0.2840.68  (Revision: 414607).
Bad build: 55.0.2841.0  (Revision: 414854).

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

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/c0fc46b641c8049da0ac0e0b3931578d02e8c5b0..5c98bb5a584a3692b8393fad6609cc9d6a0d44b0


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

@ meade : 
------------------
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/2280833002

Note: Able to reproduce the issue in Mac 10.11.6 , Win 10.0 & Ubuntu 14.04.

Comment 2 by meade@chromium.org, Nov 24 2016

Cc: meade@chromium.org
Owner: rbyers@chromium.org
It definitely wasn't my change - any mistakes there and it wouldn't compile. Rick - would you please be able to take a look?

Comment 3 by meade@chromium.org, Nov 24 2016

Cc: anan...@chromium.org
+anantha - FYI we should be ignoring CLs that just remove dead code when bisecting. If there's any extra info I can provide to help identify these, please let me know!

Comment 4 by rbyers@chromium.org, Nov 26 2016

Labels: -hasbisect-per-revision Needs-Bisect
Owner: ----
Status: Untriaged (was: Assigned)
I suspect something just went wrong with the bisect (I agree there's no way it's that change).  Can we please try doing a bisect again?

Comment 5 by brajkumar@chromium.org, Nov 28 2016

Cc: brajkumar@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision
Owner: dschuyler@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,
Good build: 54.0.2840.0
Bad build: 55.0.2841.0 

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

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/6c52e7062d5fb7cd2a1cd888f2bdea797c95e40e..a56e76de0f7e38f81f5be072f98a44516124b8bd

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.

Comment 6 by kkaluri@chromium.org, Dec 7 2016 

Just to update the latest behavior of the bug, Issue is still observed on chrome latest Dev M57-57.0.2943.0
 dschuyler@ Could you please let us know is there any recent update available on this issue?

Thanks!

Comment 7 by tbuck...@chromium.org, Jan 7 2017

Mergedinto: 675389
Status: Duplicate (was: Assigned)
►

Sign in to add a comment