Skip to content

Mobile web UI [7/7]: Give task titles the width the status select was holding - #299

Open
alex-clickhouse wants to merge 1 commit into
alex-clickhouse/mobile-sidepanelfrom
alex-clickhouse/mobile-taskcard
Open

Mobile web UI [7/7]: Give task titles the width the status select was holding#299
alex-clickhouse wants to merge 1 commit into
alex-clickhouse/mobile-sidepanelfrom
alex-clickhouse/mobile-taskcard

Conversation

@alex-clickhouse

Copy link
Copy Markdown
Collaborator

Follow-up on #271, stacked on #298. Reported from the phone: the task status select was crowding out the title.

Before

The select sat beside the title in a shrink-0 column, holding ~110px of a ~330px card whatever the viewport. The title wrapped in what was left, so an ordinary task ran to three lines:

Mobile responsiveness      [In Progress ▾]
backlog for nerve #271
(prioritized)
[In Progress]  5m ago  from manual

After

Below sm the select drops to the meta line — where 5m ago · from manual leaves room to spare — and the title takes the full card:

Mobile responsiveness backlog for nerve
#271 (prioritized)
5m ago  from manual        [In Progress ▾]

Three-line titles become two, and a screenful goes from five cards to six.

The status badge is hidden at the same breakpoint. The select beside it already names the status, so on a phone it was one value rendered twice, costing a row of vertical space to say nothing new.

How

Ordering, not duplication — one DOM, no second copy of the select to keep in sync:

layout
phone title / meta + controls
sm title + controls / meta

The meta block carries sm:basis-full so it wraps beneath on desktop, and the controls carry ml-auto so they stay right-aligned in both arrangements.

Verification

  • npm run build and eslint clean
  • 412×915: titles use the full card, select right-aligned on the meta line, badge gone, tapping the select still does not navigate into the task (the stopPropagation wrapper moved with it)
  • 1280×900: unchanged — badge present, select at the top right, meta line beneath

@alex-clickhouse alex-clickhouse changed the title Give task titles the width the status select was holding Mobile web UI [7/7]: Give task titles the width the status select was holding Aug 9, 2026
@alex-clickhouse
alex-clickhouse requested a balanced review from Copilot August 9, 2026 17:56

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Improves mobile task-card density by reallocating space from status controls to task titles.

Changes:

  • Moves status controls beside metadata on mobile.
  • Hides the redundant mobile status badge.
  • Preserves the desktop layout through responsive ordering.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

On a phone the status select sat beside the title in a shrink-0 column,
holding ~110px of a ~330px card. The title wrapped inside what was left,
so a normal task ran to three lines.

Below `sm` the select drops to the meta line, where "5m ago · from
manual" leaves room to spare, and the title takes the full card. Titles
that took three lines now take two, and a screenful goes from five cards
to six.

The status badge is hidden at the same breakpoint: the select beside it
names the status already, and one value is not worth two controls and a
row of vertical space.

Done by ordering rather than duplication — one DOM, no second copy of the
select to keep in sync:

  phone   title / meta + controls
  ≥ sm    title + controls / meta

Desktop keeps the badge, the select at the top right, and the meta line
beneath, exactly as before.

Refs #271
@alex-clickhouse
alex-clickhouse force-pushed the alex-clickhouse/mobile-taskcard branch from 4e4efcd to 8d40ebe Compare August 9, 2026 18:32
@alex-clickhouse
alex-clickhouse marked this pull request as ready for review August 9, 2026 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants