0.11.9 — measured from the window

Version 0.11.8 had gone live less than an hour earlier. Four faults, all of them visible only on a phone, all of them found in two minutes by a person who simply opened his own site.

**The panel now measures its place from the edge of the window, not from its parent.** It sat in a position relative to the button, and that looked fine as long as the bar fitted on screen. The moment the header row turned out to be wider than the window, a panel pinned to the button left the view along with it — half the list could not be read. A measured button rectangle and fixed positioning are immune to whatever the ancestors are doing: horizontal scrolling, clipping, transforms.

**The header row fits the width of the screen.** That was the cause, not the symptom. Adding a fourth element to the group of icons pushed the row wider than the window and the whole page began sliding sideways. The icon group was forbidden to shrink and the site name was allowed to: when space runs short, the name gives way, not the right edge.

**The marker sits on the mark, not on the button.** Attached to the whole button it landed above the number standing next to it — above a piece of information it has nothing to do with. It looked like an exclamation mark beside a seven.

**Opening the list counts as collecting the reward.** A mark that has been granted but not yet shown waits for the reader to act and appears on the first click. Opening the list was a click too — so the animation announced something that a moment later stood in plain text in the open panel. That one element is now an exception to the rule that any action reveals the reward, and opening the list clears everything that was waiting unshown.

Four faults, not one of which a unit test would have caught. All of them come from a narrow screen and from two independent pieces of interface meeting for the first time.