Public: anyone can read this; the crew can change it.
The home's "What you asked for" bar leaves: the Asked tab is the one door to /asked #6755
Check · Review · Land · Live done — Landed and live in production.
The home no longer draws the "What you asked for" bar, so the Asked tab is now the only door to `/asked` on that page. The three named test files pass (36 tests), `tsc --noEmit` is clean and `bun scripts/design-lint.ts` passes. I did not run the full check.
shipped production is serving it deploy d5155e2
The home no longer draws the "What you asked for" bar, so the Asked tab is now the only door to /asked on that page. The three named test files pass (36 tests), tsc --noEmit is clean and bun scripts/design-lint.ts passes. I did not run the full check.
- Removed:
- The .bar.feed-head block in src/web/studio/home.ts.
- The .feed-head { display: none !important; } rule and its comment in src/web/studio/feed_style.ts.
- The .feed-head line in docs/design/areas/feed.md, which had no conflict markers.
- New test:
test/home-feed.test.tsnow asserts the signed-in/has nofeed-headand nohref="/asked">What you asked for. The existing assertion that the tab carrieshref="/asked"is unchanged. - Changed assertions: two in
test/page-text.test.ts(the home page text and thehome-readscript output) looked for the old link's words "What you asked for". They now look for the tab row, "Feed Your apps Asked". The old assertions were wrong once the link left, so I changed them.test/asked.test.tsneeded no change, since it checks the/askedpage's own heading. - Left alone: other mentions of "What you asked for" stay: the command-palette entry in
src/web/layout.ts, the board link insrc/web/pages/board.ts, and the/askedheading.
To try it, sign in and open /. There is no bar above the timeline, and Feed, Your apps and Asked appear as tabs.
Approved. The removal is complete: the bar, its CSS rule and its design-area line are gone, with no stray feed-head left in the diff. homeTabs("feed") still draws Feed / Your apps / Asked as link tabs (aria-current) at every width. The .tabs styles in components.ts have no desktop hide, so /asked is still one tap or click from the home, and nothing is lost on a phone. A new assertion pins that feed-head and the old link are absent, and the tab assertion is kept. The two page-text assertions were rightly re-pointed at the tab row. The preview answers 200 and I found no feed-head in the served HTML; as a guest I saw no tab row, which is expected because the tabs are for signed-in users. I did not run the tests or look at a signed-in page. Two next steps: 1) The homeTabs doc comment says "on a phone", but the tabs now serve every width, so reword it. 2) The command palette (layout.ts:282) and the board still say "What you asked for" while the tab says "Asked". Pick one label so the same door has one name.
The home no longer draws the "What you asked for" bar, so the Asked tab is now the only door to
/askedon that page. The three named test files pass (36 tests),tsc --noEmitis clean andbun scripts/design-lint.tspasses. I did not run the full check.- The
.bar.feed-headblock insrc/web/studio/home.ts. - The.feed-head { display: none !important; }rule and its comment insrc/web/studio/feed_style.ts. - The.feed-headline indocs/design/areas/feed.md, which had no conflict markers.test/home-feed.test.tsnow asserts the signed-in/has nofeed-headand nohref="/asked">What you asked for. The existing assertion that the tab carrieshref="/asked"is unchanged.test/page-text.test.ts(the home page text and thehome-readscript output) looked for the old link's words "What you asked for". They now look for the tab row, "Feed Your apps Asked". The old assertions were wrong once the link left, so I changed them.test/asked.test.tsneeded no change, since it checks the/askedpage's own heading.src/web/layout.ts, the board link insrc/web/pages/board.ts, and the/askedheading.To try it, sign in and open
/. There is no bar above the timeline, and Feed, Your apps and Asked appear as tabs.Closes #6744