Public: anyone can read this; the crew can change it.

.path-head leaves the stylesheet and docs/DESIGN.md §5d #4745

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

The `.path-head` style is gone from the stylesheet and from the design doc. It had already left the page markup in #4720, so nothing still used it.

shipped production is serving it deploy e71d959

opened this

The .path-head style is gone from the stylesheet and from the design doc. It had already left the page markup in #4720, so nothing still used it.

  • src/web/style/content.ts: deleted the .path-head rule and the comment above it (the sticky file-location bar). Nothing else in the file changed.
  • docs/DESIGN.md §5d: removed .path-head from the "page furniture" class list. That line is the only change, and .path-head is the only class that left it.
  • docs/design/baseline.json: it never listed .path-head, so it is untouched.

Rebasing on main hit a conflict on that same DESIGN.md line, because main had dropped .steps from it in the meantime. I kept main's version of the line and took .path-head out of it. After the rebase there are no conflict markers in src/web/style or docs/DESIGN.md. grep -rn path-head src/ docs/ finds nothing. bun scripts/design-lint.ts is clean, and bun test test/design-lint.test.ts test/path-head.test.ts passes (17 tests).

To try it, open any file or folder view in a repository on the preview. The path bar above the contents should look and stick just as it does on production, since §5's components already draw it.

🤖 Generated with Claude Code

Closes #4693

commented

The .path-head style is gone from the stylesheet and from the design doc. It had already left the page markup in #4720, so nothing still used it.

  • src/web/style/content.ts: deleted the .path-head rule and the comment above it (the sticky file-location bar). Nothing else in the file changed.
  • docs/DESIGN.md §5d: removed .path-head from the "page furniture" class list. That line is the only change, and .path-head is the only class that left it.
  • docs/design/baseline.json: it never listed .path-head, so it is untouched.

Rebasing on main hit a conflict on that same DESIGN.md line, because main had dropped .steps from it in the meantime. I kept main's version of the line and took .path-head out of it. After the rebase there are no conflict markers in src/web/style or docs/DESIGN.md. grep -rn path-head src/ docs/ finds nothing. bun scripts/design-lint.ts is clean, and bun test test/design-lint.test.ts test/path-head.test.ts passes (17 tests).

To try it, open any file or folder view in a repository on the preview. The path bar above the contents should look and stick just as it does on production, since §5's components already draw it.

🤖 Generated with Claude Code

Approved

Dead-code removal, verified: no markup, source or script references .path-head any more (only test/path-head.test.ts, which asserts it is absent), the preview serves 200 and its stylesheet no longer contains the rule, and DESIGN.md §5d drops exactly that class. No behaviour, security or JS-off impact. Two next things: (1) in the pull, state that the sticky path bar is now drawn by §5 components, since the description claims it still sticks as on production and the preview shows no .path-head to confirm that; (2) keep sweeping the remaining unused classes in the page-furniture list the same way so the list keeps shrinking.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs