I find Japan-shaped holes in global software

Short summary

A class of software bugs occurs when apps don't properly handle Japanese IME input, causing forms to submit on the Enter key that confirms kanji conversion instead of finalizing input. The fix is checking `!e.nativeEvent.isComposing` on keydown handlers, but teams consistently miss secondary inputs like search boxes and rename fields because they don't test with IME. The same blind spot produces related bugs in date validation (era-based years), name fields (family-name-first), and character width handling.

• •Japanese IME bugs occur when Enter key confirming kanji conversion triggers unintended form submission
• •One-line fix: check `!e.nativeEvent.isComposing` flag, plus fallback for keyCode 229
• •Structural testing gap: primary inputs are guarded but secondary ones (search, rename, tags) are missed

Generated with AI, which can make mistakes.