The post is a small software archaeology story about a very specific bug with big lessons. Polish typists often entered Ś with Alt+S on older layouts. On Windows, the right Alt key is often exposed as AltGr, which many apps and browsers saw as Ctrl+Alt. That meant websites that trapped Ctrl+S to override browser save behavior could accidentally swallow a normal letter input. The article walks through how that happened, why it was so persistent, and how a one-line modifier check fixed it.
People reading it landed on a broader point fast. Keyboard handling is still full of traps in 2026. Multiple commenters said current Microsoft products are repeating the same class of mistake, with Copilot 365, Edge, and Teams interfering with Polish characters or popping up UI on the same keystrokes. Others sharpened the technical lesson. The bug was not really about Polish. It was about developers hard-coding shortcut logic around a US keyboard model and assuming modifier keys have stable meanings across operating systems. A few comments pushed that further and argued browsers still make this too awkward by exposing raw modifiers instead of a clean normalized key-combination value.
A second technical thread added a useful text-processing wrinkle.
Unicode normalization mostly decomposes Polish diacritics into base letters plus marks, but ł does not. That makes “strip diacritics” approaches unreliable for full-text search and transliteration. One Polish speaker noted that users generally do not expect ł to match l in search, which undercuts the common instinct to fold everything to
ASCII. The practical read is straightforward: shortcut code and search normalization both look trivial until you leave English, and then years-old assumptions start deleting letters, breaking search, or triggering the wrong feature.