Inconsistent Chrome credit card expiration autofill
Reported by
jonathan...@gmail.com,
Aug 30
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: 1. Have a saved credit card with non-2020 year (e.g. 2023) 2. Load page with form with credit card inputs (here's a fiddle https://jsfiddle.net/JonathanN/j054kbgx/) 3. Click on credit card inputs and use autofill to populate 4. The format of credit card expiration field will vary depending on random factors like presence of label, autocomplete="cc-exp" attribute, and maxlength. Also, version of Chrome seems to matter. I tested Chrome on Windows and Chrome on Android and got different results. What is the expected behavior? If expiration date field has maxlength="5", Chrome should autofill with MM/YY format. What went wrong? It fills MM/YYYY format despite maxlength="5" without autocomplete="cc-exp", or if Chrome on Android is used. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 66.0.3359.139 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Fiddle: https://jsfiddle.net/JonathanN/j054kbgx/
,
Aug 31
,
Aug 31
Unable to reproduce the issue on chrome stable 68.0.3440.106 using Windows 7. Attaching screen-cast for reference. Steps: --------- 1. Launched reported chrome 2. Navigated to given Chrome://settings/Autofill >> added credit card details 3. Navigated to given URL " https://jsfiddle.net/JonathanN/j054kbgx/ " As we are able see the expiration date field auto fill with MM/YY format. @Reporter: Could you please upgrade to latest chrome stable 68.0.3440.106 and 69.0.3497.57, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel " Let us know whether issue still persists. Also mention that issue seen on windows/ Android. Thanks.!
,
Aug 31
,
Aug 31
,
Aug 31
For some reason the same forms produce different results on my actual site, as referenced in the fiddler. https://www.wheelerfleet.com/Content/test.html I loaded up this test page with the latest Chrome, and I see MM/YYYY format for all but the 3rd form. Of note, I had to load a VM to get the latest Chrome, as my company is restricting updates. On the other hand, it is a clean install with no associated user data, so a good test platform.
,
Aug 31
Version info: Google Chrome 68.0.3440.106 (Official Build) (32-bit) (cohort: Stable) Revision 1c32c539ce0065a41cb79da7bfcd2c71af1afe62-refs/branch-heads/3440@{#794} OS Windows JavaScript V8 6.8.275.26 Flash 30.0.0.154 C:\Users\IEUser\AppData\Local\Google\Chrome\User Data\PepperFlash\30.0.0.154\pepflashplayer.dll User Agent Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Command Line "C:\Program Files\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end Executable Path C:\Program Files\Google\Chrome\Application\chrome.exe Profile Path C:\Users\IEUser\AppData\Local\Google\Chrome\User Data\Default
,
Aug 31
Honestly, the only place form #3 doesn't work (produce MM/YY autofill) is on the actual checkout web page with Android. I can't repro that particular behavior on my test page, Android or otherwise. I even mimiced the ajax load of the form like the original. There's a lot going on on the original page. Our primary customers are desktop, so having an option that works on desktop may have to suffice.
,
Aug 31
I started adding javascript libraries from my checkout page to the test and managed to reproduce the error. It looks to do with jquery inputmask library. It might be overwriting maxlength at runtime, not sure. I am going to try using another library or drop masking altogether.
,
Sep 5
Parastoo, could you please take a look when you get the chance? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by viswa.karala@chromium.org
, Aug 30