"Save passwords.." prompt doesn't appear for Google Account which is connected to Chrome
Reported by
depy45...@gmail.com,
Dec 12 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Sign-into Chrome using a Google account 2. Go to any Google product's login page and enter the the Google account's username and password 3. Continue to log-in What is the expected behavior? Generally it should display the lock icon in the address-bar that prompts the user to save password for that site. What went wrong? The browser doesn't ask the user to save the password for the Google account. If the Google account is connected to Chrome, and you sign-into the account in a Google product it doesn't show up the prompt to save the password. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Dec 15 2016
depy45631@ Could you please let us know the accounts which you used to sign into "chrome browser" and "Google product login" are same or different ???
,
Dec 15 2016
@kkaluri it is the same Google account, the problem of the "Save password" prompt not appearing is specific to the Google account that is signed into Chrome browser. So yes, those are the same account
,
Dec 22 2016
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref bug 684919
,
Mar 13 2017
,
Mar 15 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, Dec 13 2016