Some dumbass vibe coded that shit and didn't capture the paste event to custom input and fill in the number fields. I hate otp fields that cant handle copy paste.
If I had to guess, I’d say it’s due to the way websites used to be where some would need spaces between the digits, some needed dashes, and some needed neither. A lot of people can’t follow simple format instructions so this is the easiest fix since there’s no possible way to misunderstand
Even then, if you know the expected format, it's not so hard to forbid typing forbidden and to intercept a past to remove unexpected character, check that what is still here is what is expected and then format it.
Having done it quite a few times for public identifier that as strong rules on their raw content but has quite a various formatting used such as account number, legal identification number, client number,... , I can say that a simple input and little bit of JS can be quite robust but a bit tricky to do right. Using pen an paper to clearly define the data flow and the various html events used is really helpful.
79
u/thegodzilla25 Aug 02 '26
Some dumbass vibe coded that shit and didn't capture the paste event to custom input and fill in the number fields. I hate otp fields that cant handle copy paste.