New issue
Advanced search Search tips

Issue 921453 link

Starred by 1 user
Status: Assigned
Owner:
ccameron@chromium.org
Cc:
ftirelo@chromium.org
nyerramilli@chromium.org
kolos@chromium.org
rbasuvula@chromium.org
vasi...@chromium.org
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Password suggestion drop-down turns transparent in facebook.com.

Project Member Reported by shru...@virtusa.com, Jan 14 
Chrome Version: 73.0.3670.0 (Official Build) Revision	1ad472e9f385f6769ab1d1709a2ba26218522c96-refs/branch-heads/3670@{#1}(64-bit)
OS : Mac(10.13.6, 10.13.1, 10.14.2)

Steps to reproduce:
1. Launch chrome and Navigate to facebook.com
2. Open wrench menu and under 'More Tools' ,click on 'Create Shortcut'.
3.'Create Shortcut' Dialogue will open ,check the 'Open as window' option.
4. Navigate to chrome://apps and click on facebook.com shortcut.
5. Click on 'New Password' so that password generation auto-populate ,hover mouse and observe.


Actual Result:Password suggestion drop-down turns transparent.
Expected Result: Password suggestion drop-down should not turn transparent.

This is a regression issue broken in M-73 and will soon update bisect information:
Good Build :73.0.3640.0 
Bad Build : 73.0.3641.0 


Kindly refer the attached screen-cast.
https://drive.google.com/open?id=1-b6BaJZa5P-ygl8sR6XFHJfytHuf_PHe
Thank You..

Comment 1 by battre@chromium.org, Jan 14

Cc: ftirelo@chromium.org kolos@chromium.org vasi...@chromium.org
Status: Available (was: Unconfirmed)

Comment 2 by shru...@virtusa.com, Jan 14

Labels: hasbisect
Owner: ccameron@chromium.org
Status: Assigned (was: Available)
Update :
Bisect-info:
https://chromium.googlesource.com/chromium/src/+log/e843814f60dbfbd9ae70daf200326e72cc322418..bdfa3bb74e76d0da628f876469af1d94bd5bad83

Suspect:https://chromium.googlesource.com/chromium/src/+/8b9a5b8dfaeb5152fbc1f8c17ad7c11e604d56d3

@Christopher Cameron : 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.

Note: 
1. Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message for above range. (tried on other machines but still getting the same error again)
2. Hence providing suspect via perform Chromium bisect .
3.Issue is not seen on OS: Windows(7,8,10) and Linux(14.04 LTS).

Thank You...

Comment 3 by vasi...@chromium.org, Jan 14 

Correct, it's kHostWindowsInAppShimProcess experiment that leads to the behavior.
►

Sign in to add a comment