Why Your Input Length Limit Is Wrong

Standard string length checks (UTF-16 code units, bytes, or code points) do not match what users perceive as a single character, because composed characters, Indic scripts, and emoji sequences form multi-code-point grapheme clusters. Enforcing input limits at the wrong boundary can corrupt text by splitting combining marks or emoji joiners. The recommended fix is to measure length using grapheme clusters via APIs like Intl.Segmenter.