Skip to content

fix(build): restore 44px mobile tap targets on workspace artifact tabs (#1042) - #1043

Merged
developer-ainative merged 1 commit into
mainfrom
bug/issue-91-mobile-tap-targets
Oct 9, 2026
Merged

developer-ainative merged 1 commit into
mainfrom
bug/issue-91-mobile-tap-targets

Conversation

@developer-ainative

Copy link
Copy Markdown
Contributor

Summary

Found during pre-summit mobile QA (375×667) against real production: the workspace artifact breadcrumb tabs (`.m-crumb`) render at ~24px tall on mobile — under the 44px tap-target floor every other control on the screen already respects — with zero mobile rule covering them.

Also root-caused: a prior mobile fix for the phase-bar wrapper still targeted the stale `.m-actbar` selector, dead since `JourneyBar.tsx`'s refactor wrapped it in `.m-journey-bar > .m-journey-phases` instead — the wrap/padding treatment had silently stopped applying.

Fix

  • `app/modernist.css`: `.m-crumb { min-height: 44px }`, retargeted the dead `.m-actbar` rule to `.m-journey-phases`

Test plan

  • `npx vitest run tests/app/modernist-mobile.test.ts` — 22/22 pass (TDD red confirmed first)
  • Full suite — matches pre-existing baseline exactly, verified via stash/pop
  • `npx tsc --noEmit` — clean
  • Playwright verification against JourneyBar.tsx's real DOM structure and the actual fixed stylesheet

Closes #1042

(Note: this fix was accidentally first pushed to the wrong repository, AINative-Studio/cody-builder — that PR/issue have been closed. This is the correct, re-targeted version.)

#91)

.m-crumb (the artifact breadcrumb tabs in JourneyBar.tsx — the primary
way a founder switches between a build's 14 artifacts) measured ~24px
tall on a 375px phone, confirmed live against production — well under
the 44px floor every other interactive control on the same screen
already respects (#339/#940). No mobile rule had ever covered it.

Also retargets the #940 phase-bar mobile rule from the stale .m-actbar
selector to .m-journey-phases, its real wrapper since JourneyBar.tsx
merged the old ActBar + PathBreadcrumb components — .m-actbar no
longer matches anything in the rendered DOM, so that rule's intended
wrap/padding treatment had silently stopped applying (the sibling
.m-acts/.m-actbar-right rules kept working since they key off their
own class names, independent of the dead wrapper selector).

Closes #91
@developer-ainative
developer-ainative merged commit dc6a7fa into main Oct 9, 2026
1 check passed
@developer-ainative
developer-ainative deleted the bug/issue-91-mobile-tap-targets branch October 9, 2026 09:14
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.

Workspace artifact tabs (.m-crumb) miss the 44px mobile tap-target floor; prior phase-bar mobile fix is dead CSS after JourneyBar refactor

1 participant