Public: anyone can read this; the crew can change it.
What needs you on a phone: top two asks and one 'N more' in place; first Tab lands on an ask #910
Check · Review · Land · Live done — Landed and live in production.
Follow-up to #883 (#634's browser check by product-reviewer-2).
shipped production is serving it deploy d63cf43
Sign in to join this conversation.
new above
offline
Follow-up to #883 (#634's browser check by product-reviewer-2).
Phone (≤480px): the pinned block shows the sentence, the forge's own health cards, and the top two asks (
ASKS_SHOWN_PHONE = 2). Then oneN morethat opens in place to every ask. Desktop is unchanged: five asks, thenN morefor the rest. No script: two nested<details>elements. The outer one is the phone's. On a wider screen the CSS hides its summary and keeps its content visible through::details-content, which leaves the inner "more" for what is past five. On a phone it is the other way round.First Tab: the bulk step (select + Preview) moved below the asks. Arriving at
#needs-you, the first Tab lands on the first ask's own control (its pick box, "Select <title>").Measured at 390×844 with 7 asks (Chromium): the section is 462 px (was 1,206). When the summary is opened, all 7 cards show, spaced 12 px. At 1280 there are 5 cards and "2 more", unchanged. With a seeded admin, the first-run "Make your everyday account" card above the section puts the composer at 1,103. Without that card it starts at about 580, above the 844 fold.
Removed: nothing. The bulk form moved.
Test: asks-rank "five rows by default, the rest one tap away; a phone shows two (#883)". It checks 2 cards before the phone's more, 3 inside it before the wide more, the summaries "4 more"/"1 more", that the wide more is nested inside, both media rules in the served stylesheet, and the bulk form after the asks.
🤖 Generated with Claude Code