Expiry dates for both my saved payment cards shifted by one month |
|||
Issue descriptionChrome Version : 64.0.3282.186 OS Version: OS X 10.13.3 URLs (if applicable) : gresik.cz (eshop) / https://platebnibrana.csob.cz/ (payment site run by a bank) What steps will reproduce the problem? 1. get some stuff into your cart, proceed to chekout 2. choose to pay by by card 3. select a card autofilled by Chrome What is the expected result? The correct expiry date appears for my card. What happens instead of that? The expiry date was shifted by one month (05/20 instead of 04/20). I corrected it and continued with the process. The payment failed (due to some error on the side of the bank) so I picked my other card. The expiry date was again shifted by one month (03/20 instead of 02/20). I corrected it and finished the payment. When I visit the payment portal again (with another order), I get correct expiry dates filled in for both these cards. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
,
Mar 26 2018
I'm thinking it could be a website issue i.e. that we are filling the wrong index in the <select> field.
,
Mar 26 2018
jkrcal@, an HTML dump of the (empty) form would be useful, if you could send to the team directly
,
Mar 26 2018
,
Mar 26 2018
I'd be happy to help investigate the server side, but I'd need your explicit permission to look into the logs for your account first (and which account it is). It sounds to me like the HTML dump would be a better first step, as I haven't seen any month-shifting issues with cards from Payments before.
,
Mar 27 2018
I was able to repro this. Not sure where exactly this shift is coming from. The field is a text input, which we determine to have type CREDIT_CARD_EXP_DATE_2_DIGIT_YEAR. Testing of similar fields seems to work ok.
,
Mar 28 2018
These are probably local cards (one of them is both local and from payments.google.com) the local one appearing higher in the list on chrome://settings/autofill). Is it correct that due to #6, the request for html dump from #3 is obsolete?
,
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 rouslan@chromium.org
, Mar 26 2018Components: UI>Browser>Autofill
Owner: rogerm@chromium.org
Status: Untriaged (was: Unconfirmed)