Autofill incorrectly suggests credit card expiry date for non credit card fields
Reported by
damian.n...@gmail.com,
Nov 9 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Steps to reproduce the problem: 1. Make sure you have a credit card added to your Chrome autofill settings 2. Open a html file containing the following form(Codepen example - https://codepen.io/damian-1478604314/pen/PbqeqG) on an HTTPS connection otherwise credit card autocomplete isn't triggered. ``` <form autocomplete="off"> <label for="ticket_amount">Ticket amount</label><br /> <input type="text" name="ticket_type[total]" id="ticket_amount" autcomplete="off"><br /> <label for="address1">Address line 1</label><br /> <input type="text" name="address1" id="address1"><br /> <label for="address2">Address line 2</label><br /> <input type="text" name="address2" id="address2"><br /> </form> ``` 3. Double click the 'Ticket amount' field 4. The credit card autofill suggestion appears suggesting the card expiry date What is the expected behavior? I'd expect the credit card autocomplete not to appear. What went wrong? The credit card autofill appears even though the fields are in no way related to credit cards, and the `autocomplete='off'` attribute is being ignored. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 54.0.2840.87 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0
,
Nov 10 2016
[Chrome mac triage] This is not Mac specific. Verified the issue on both Linux and Mac. zkoch@ Can you take a look?
,
Nov 10 2016
I am also having issues with a field named `client[vat]` being populated with the state/county name. Looking at this issue, I suspect the two could be related. Code to reproduce: <form> <input type="text" name="address1"> <input type="text" name="address2"> <input type="text" name="city"> <input type="text" name="postal_code"> <input type="text" name="client[vat]"> </form>
,
May 1 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||
►
Sign in to add a comment |
||||
Comment 1 by shivanisha@chromium.org
, Nov 9 2016