New issue
Advanced search Search tips

Issue 610883 link

Starred by 6 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Seperate setting for credit card from Auto-fill

Reported by loorong...@gmail.com, May 10 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36

Steps to reproduce the problem:
1. Enable Auto-fill in settings.
2. Go to any website that ask for credit card information.
3. Type the information and click submit.

What is the expected behavior?

What went wrong?
After submitting, Chrome ask the user if he want to save the credit card information.

Did this work before? No 

Chrome version: 50.0.2661.94  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0

tl;dr
Allow to disable credit card auto-fill while enabling the other parts of auto-fill.

Many users regard credit card number as a highly sensitive information and therefore want credit card information has a separated settings from normal auto-fill.

Original product forum post:
https://productforums.google.com/forum/#!topic/chrome/c6zMDKKnW7Y

(If this feature is never going to be implemented, please give an explanation so that I can forward it to the users.)
 

Comment 1 by bro...@brolin.be, May 18 2016

I concur that the offer by Chrome to save credit card details entered by the user should include a choice/option to never remember credit card details.  I do not want my Web browser to remember my credit card details.  I suppose the generalised solution is to add options for “Never remember this credit card” and “Never remember any credit card” in case a user wants to remember details for some credit card accounts but not for others.  I have to manually review and pay bills for some services every month;  it frustrates me that Chrome offers to save my credit card details every time.

Comment 2 by b...@chromium.org, Jul 25 2016

 Issue 630894  has been merged into this issue.

Comment 3 by b...@chromium.org, Jul 26 2016

 Issue 631505  has been merged into this issue.
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 27 2017

Status: Archived (was: Unconfirmed)
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