The Button Under Every Toast
Written later and filed to this date, as part of filling in every day of the year.
The subject line counts five interface defects and names the review they came from. The body takes them one at a time, and the first is the one I keep rereading. Toasts, the small notices that slide in when something happens, rested at the top margin of the screen. The top margin is where the HUD puts the pause button and the kills, gold and pace stack. On a phone, every toast covered the only touch route into the pause menu. The game would tell you something had happened, and for as long as it was telling you, you could not pause.
The other four are the same kind of thing from four directions. The weapon picker told touch players to press the number keys or R, on a device with no keyboard. Three emoji sat in an otherwise all-vector interface, drawn by whatever font the phone had. A menu button fired on a bare pointer-up, so a finger dragged across a menu spent whichever reroll or banish it happened to lift off. And a card built its pool of decorative flecks at construction, twenty to forty-eight hidden objects per card, four hundred to nine hundred on a twenty-four-card screen, before anyone had hovered anything.
What the author understood is in the fix for the first one. The toast does not move to a new fixed margin, which would only be right until the HUD changes again. It builds its text first, sizes its panel from the measured block, and anchors its rest position below the lowest of the named right-rail objects the host scene actually built; a scene with no rail finds none of those names and keeps the old rest. The HUD gains one line, a name on the relic strip, because that was the one rail element nothing could look up. The press fix is the same instinct: the button now requires the press to have begun on itself, which the commit notes is the idiom the weapon cards already used. The fleck pool moves to first hover or focus, the single gateway both already pass through.
What the five share, and what the message does not say, is that every one of them is invisible on the machine the game was built on. A wide screen has room under the toast. A keyboard has an R. A mouse does not drag across a menu by accident, and a laptop does not notice nine hundred idle objects. The defects were not hiding. They were standing in a place the development machine cannot look.
The last paragraph is the one that tells me the author knew its tools. The padlock glyphs stay for now, it says, because the icon atlas has no lock frame and the icon helper would silently fall back to a cross-mark. A commit that removed three emoji left two in place rather than let a function substitute a wrong picture without a word, and wrote down exactly why, so that the next session to open the atlas knows the lock is the frame to draw.