Title basically. Most forms require MM/YY, but bitwarden always tries to do MM/YYYY (despite me filling field as just last two digits). Basically, I can never autofill card information, making feature almost useless.
If there are plenty of MM/YYYY forms, distinguish between them? Or maybe let us select between idk.
@Lippiece there are many feature requests for the team to consider, let’s keep criticism constructive, you can review the community guidelines at any time.
Rest assured your feedback has been passed along.
I am wrong and responded out of emotions, please disregard my previous message. This is actually a bug, see pull, issue.
Although I still don’t see any point using this forum when you already have GitHub.
Thanks, I’ve deleted the post above since the comment was removed 
the forum is a space for discussion, community help, feature requests etc…
When there is a specific bug report, those conversations take place on Github.
I’m having issues with numerous pages where Bitwarden autofills the expiration date as “02/27” when the expiration date for my credit card is 03/2027.
What is the best way to fix this? It last happend when ordering from Bose.com, but it’s happening on a lot of websites.
The best way to deal with it is to submit an Autofill Failure Report using the following form:
In my experiments on bose.com, the expiration date for a card with 03/2027 would have been autofilled as “02/70”, not “02/27”, though. Incidentally, it is possible to correctly autofill the Bose card payment form if you delete the stored expiration date and instead create a custom text field with the name regex=adyen-checkout-encryptedExpiryDate-[0-9]{13} and a value in the format MMYY. This may not be a practical solution (unless you make frequent purchases from Bose), but I share this detail because it suggests that it should be possible for Bitwarden to fix the issue for this site.
If this is not an exaggeration, then please provide a list, and confirm that the 03/2027 card is always autofilled as “02/70” on all of the affected sites. If the exact same behavior is occurring on a large number of sites (especially on sites that were autofilling correctly previously), then it might be a bug — which should be reported on Github.
So the correct place to report it is on GitHub and not here?
Sorry, I don’t have the time to submit bug reports on multiple platforms. I’ve previously used the report auto-fill failure form on a bunch of websites. To date, not a single one of them has been fixed.
How about first just responding here to supply the information that I had requested above — and then, if it seems likely that there is a bug, perhaps someone else will report it on Github on behalf of everybody affected.
Thanks. Will keep a list of websites that do this going forward.
