Keep the lesson for the next incident
Compare overflow conditions
Align viewport, zoom, browser, page state, content length, controls, tables, navigation, and blocked task across episodes. Identify repeated constraints and separate one-off extreme content.
Define the reflow contract
Document which content wraps, which regions scroll intentionally, how primary actions remain reachable, and where focus moves after errors or menus. Keep the contract tied to user tasks.
Set a recurrence check
Trigger a narrow review after typography, navigation, control grouping, table, or long-content changes. Name representative widths and fixtures that must be checked before calling the layout stable.
What to carry forward
The lesson should preserve one content-aware responsive contract and a recurrence rule for layout changes. Treat stability as provisional until later long-content and recovery states remain usable at narrow and enlarged views. Preserve representative narrow widths and long-content fixtures in the layout review, and rerun them after typography, navigation, controls, tables, or spacing changes. Record the minimum content lengths that exposed the issue, not only the viewport width.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow