I’m finding that the autofill credit card feature doesn’t work as desired the majority of times.
It seems to wig out when sites ask for credit card expiration dates in MM/YY format instead of MM/YYYY format. Sometimes it fills out a credit card’s expiration as 01/20 and sometimes I’ve even seen it fill it out as 20/23. When it asks in MM/YYYY format, I’ve never seen it not work as expected.
Is there a workaround to get this to work correctly?
PR #3768 apparently only addresses the problem when it is caused by the presence of Cyrillic characters in the expiration date placeholder.
@southerndoc Can you provide some examples of where the MM/YY format is not correctly filled? Perhaps if these can be diagnosed, someone will be able to do another PR to fix the issue on additional sites.
I’ll keep a list of sites going forward. Unfortunately, I order so much crap that I don’t remember which ones gave me issue. LOL
I DM’d you a website. Unfortunately the URL gives away my location.
The expiration date for my card is 03/2027. It entered the expiration as 20/27. I have a screen shot but I do not see where I have an option to post it.
I have a similar issue with the postal code/zip code field in the credit card file never auto filling. I may try to create a custom field based on a few fieldIDs to see if that solves the problem.
Based on testing, it seems like the auto-filling of credit card expiration dates requires the site to use a parameter named
placeholder in the HTML code for the input field. This would have a value like
placeholder = "MM/YY" to signal the expected format. If this is not present, then Bitwarden cannot determine how to properly format the expiration date.
So I believe the issue is not specifically related to the
MM/YY date format (for example, this format is autofilled correctly on DoorDash.com and other sites), it is just a problem when the credit card form does not include the placeholder template that is required for the auto-filling to work correctly.