Issue metadata
Sign in to add a comment
|
Credit Card information must be separated from autofill
Reported by
o...@bekmezci.net,
May 4 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Users must be able to disable Credit Card info saving without disabling auto-complete 2. Saving Credit Card function should have its own configuration possibility independent of auto-complete. Just like passwords. Passwords are kept for auto-filling but they are configured by users in different manner completely independent of standart auto-fill called auto-complete. What is the expected behavior? Chrome should not keep Credit Card information while the great fiction Auto-complete is enabled. What went wrong? In order to have the very useful function of auto-complete, the users must bother with a pop-up question of keeping Credit Card information. Did this work before? Yes I do not remember. Chrome version: 57.0.2987.133 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0
,
May 11 2017
Assuming this might be a feature request, changing the status to Untriaged, so that the issue would get addressed. Thank You.
,
Sep 3 2017
I agree. Protecting sensitive, regulated data like CC numbers should be separate from form autofill.
,
Dec 1 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, May 10 2017Labels: Needs-Milestone