Open dpikt opened 4 years ago
+1 to this. What about an expiration date input?
Like for cards?
Yep! Working across a few different payment providers I've found that that field is often not included in the fields that are provided via iFrame.
We have a reference implementation of an input with validations and an input mask in SC
@dpikt I want to research this a bit more. In another article from the same author (about phone numbers) he lists out some cons of splitting fields that he doesn't mention in the other article: https://uxmovement.com/forms/bad-practices-on-phone-number-form-fields/ So I think I'd want to weigh all the pros and cons and also try to find some usability test research.
Following the example set out here: https://uxmovement.com/forms/bad-practices-on-birthdate-form-fields/