design(board): give mobile column-header actions roomier tap spacing - #218
Merged
Conversation
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
1 participant
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.
Design-polish pass — a mobile-zoom hunt on the board. Each column header carries 5 action icons (move ‹ ›, rename, duplicate, delete). On desktop they hover-reveal (DES#175), but on touch (no hover) all five show at all times, packed at
gap: 4px/padding: 2px— a cramped, jammed strip that's hard to tap the right icon in.Fix (CSS-only, tokens only)
In the
@media (max-width: 600px)block, give the column-header action buttons roomier spacing (gap: 10px,padding: 4px) so they read as distinct, comfortable touch targets spread across the header rather than a crammed cluster. Desktop is unchanged (keeps its compact hover-revealed cluster).Before → after
Full quality gate green; presentational-only. Verified against the sandbox (
AWS_PROFILE=personal).Note: fully tucking these behind a "⋯" overflow menu (Asana's mobile pattern) would be cleaner still, but that's a new component/behavior — beyond this loop's visual-token mandate. The spacing improvement is the safe in-scope win; the move ‹ › chevrons stay visible since they're the primary way to reorder columns on touch.