feat(outline): PROG-80 jump to issue from Outline via a far-left gutter link#53
Merged
Conversation
…gutter The Outline's only door to an issue's page was a trailing `…` link hidden in an `opacity-0 group-hover:opacity-100` cluster on the right edge. Touch has no hover, so on a phone there was no way to reach an issue from the Outline; even on desktop the control sat at a right edge that shifts with the row's text. Move that jump control to a fixed gutter at the far left of every row: a per-row `<Link>` rendered as a 24x24 three-dot SVG tap target. Full opacity on mobile (always reachable, no hover), `sm:opacity-40` firming to full on hover/focus-within/focus-visible on desktop — discoverable there too, a strict improvement over the old fully-hidden state. Arc assignment stays a desktop hover affordance (navigation-only control moved). Capture rows gain a matching empty gutter so their `+` bullets stay aligned with the issue bullets. Docs: record the rationale as DECISIONS `### PROG-80` and update the Outline entry in REFERENCE.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PROG-80 — Make it easier to jump to issue view from Outline mobile view
Problem
On a phone there was no way to open an issue's page from the Outline. The
only jump control was the trailing
…link, tucked into anopacity-0 group-hover:opacity-100cluster on the right edge — touch has nohover, so it never appeared. On desktop it was reachable but sat at a right edge
that shifts with each row's text width.
Change
Per the issue, the jump control moves to a fixed gutter at the far left of
every row, and it becomes touch-reachable:
<Link>(a real anchor) rendered as a24×24 three-dot SVG tap target, in one predictable spot at every depth.
full (mobile primary); desktop uses
sm:opacity-40firming to full onhover /
group-focus-within/focus-visible. The outline stays calm on awide screen but the affordance is now discoverable — a strict improvement over
the old fully-hidden state (the "improve desktop too" half of the ask).
ArcMenu(depth-0) stays a desktop hover affordance (already mobile-unreachable before,
and reachable from the full issue page — no regression).
+bullets stay alignedwith the issue bullets now pushed right by the open-link.
Verification
bun run check(tsc) clean;bun test— 84 pass / 0 fail.the left gutter at every row/depth; mobile computed opacity = 1 (visible with
no hover); tapping it navigates to
/issue/<KEY>.Notes
docs/DECISIONS.md### PROG-80(rationale + rejectedalternatives) and the Outline entry in
docs/REFERENCE.md.adjacent controls to the same page reads as redundant and risks mis-taps while
editing a title.