Skip to content

fix(ui): raise remaining interactive tap floors - #2424

Merged
BigSimmo merged 8 commits into
mainfrom
claude/ds-h36-tap-floors
Aug 27, 2026
Merged

fix(ui): raise remaining interactive tap floors#2424
BigSimmo merged 8 commits into
mainfrom
claude/ds-h36-tap-floors

Conversation

@BigSimmo

@BigSimmoBigSimmo commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Summary

Verification

  • [x]
    pm run format on changed files (included in this commit)
  • [ ]
    pm run verify:pr-local

Verification not run: approved 6-PR split publication; local format applied to the replayed slice. �erify:pr-local, lint, typecheck, unit, and hosted CI were left unrun by request.
UI verification not run: �erify:ui left unrun by request.

  • [ ]
    pm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed
  • [ ]
    pm run verify:release before release or handoff confidence claims

For retrieval, ranking, selection, chunking, source/citation rendering, or answer-contract changes, �erify:pr-local runs eval:rag:offline automatically. Run the offline command directly during iteration before spending a live eval.

  • **
    pm run eval:retrieval:quality (must stay 36/36) when retrieval, ranking, selection, chunking, or scoring behavior changed** — CI cannot run it (needs live keys), so run it locally and paste the summary. A metadata/governance-weighting change once buried correct docs (recall 1.0→0.76) and only this eval caught it.
  • [ ]
    pm run eval:rag -- --limit 15 +
    pm run eval:quality -- --rag-only when answer generation, the synthesis prompt, or answer post-processing changed (grounded-supported must not drop; citation-failure 0)
  • [ ]
    pm run check:production-readiness when clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changed
  • [ ]
    pm run check:deployment-readiness when deployment startup, hosting, or rollout behavior changed

Risk and rollout

Complete this section for clinical, data, API, auth/privacy, workflow, dependency, build, or deployment changes.

  • Risk: low — tap-target CSS on existing interactive controls; no retrieval, ingestion, or auth changes.
  • Rollback: revert this PR.
  • Provider or production effects: None
  • RAG impact: no retrieval behaviour change — design-system tap/chrome/tokens only.

Clinical Governance Preflight

N/A — design-system tap/chrome/tokens only; no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical-output contract changes.

Notes


Note

Low Risk
CSS tap-target and one local Checkbox adoption plus settings scroll styling; no auth, data, or retrieval changes.

Overview
Standardizes interactive hit areas on documents, calculators, compare, forms, tools, settings, and chip remove controls by replacing ad-hoc min-h-8/min-h-9/min-h-10 (and similar) with the shared min-h-tap token, and drops redundant height classes where shared recipes (e.g. floatingControl) already enforce the floor.

Document admin swaps the native “Needs review” queue checkbox for the design-system Checkbox from choice.tsx, and gives several <summary> rows min-h-tap for disclosure tap targets.

Chip removable chips center the remove button with min-h-tap / w-8 so the painted chip stays compact while the hit target meets the production floor.

Settings dialog removes Tailwind scroll-smooth from the scroll port and tightens comments/behavior around section scrolling under reduced motion vs smooth scrollTo.

Adoption/docs (slice F):adoption-manifest.json and COMPONENTS.md refresh counts and maturity rows (Checkbox, FieldHint, FieldError now show product imports / v2 mount); P1 outline groups AppliedFilters/CopyButton with other spec-only items instead of a separate “built but unregistered” callout.

Reviewed by Cursor Bugbot for commit afce182. Configure here.

Primary actions on documents, compare, tools, calculators, forms, and chips still used sub-48px heights. Raise those controls to the tap floor so phone targets stay reachable without shrinking CTAs.
Co-authored-by: Cursor <cursoragent@cursor.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitaiBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 57 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 102 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6bc5b16e-5209-47f4-9abb-696faf14d819

📥 Commits

Reviewing files that changed from the base of the PR and between 989767a and 08a3af9.

⛔ Files ignored due to path filters (2)
  • docs/design-system/COMPONENTS.md is excluded by !docs/**, !**/*.md
  • docs/design-system/adoption-manifest.json is excluded by !docs/**
📒 Files selected for processing (13)
  • src/components/calculators/calculator-ui.tsx
  • src/components/calculators/clinical-console.tsx
  • src/components/clinical-dashboard/DocumentManagerPanel.tsx
  • src/components/clinical-dashboard/document-admin.tsx
  • src/components/clinical-dashboard/document-ui.tsx
  • src/components/clinical-dashboard/settings-dialog.tsx
  • src/components/compare/compare-catalog-picker.tsx
  • src/components/compare/compare-empty-state.tsx
  • src/components/forms/form-detail-page.tsx
  • src/components/forms/forms-search-results-page.tsx
  • src/components/tools/tools-search-results-page.tsx
  • src/components/ui/chip.tsx
  • tests/ui-v2-components.dom.test.tsx

Comment @coderabbitai help to get the list of available commands.

@cursor

cursorBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_cb34185d-0a75-4698-982a-e8f68dd4f020)

@github-actions

github-actionsBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

CI triage

CI failed on this PR. Automated classification of the 3 failed job(s):

  • Lighthouse budgetmain-side: the same job also failed on the latest completed main CI run.
  • Unit coverageneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • PR requiredmain-side: the same job also failed on the latest completed main CI run.

Compared with main CI run #14256 (failure).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

@cursor

cursorBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6ab213b0-1a9b-478e-ac52-ca7296a777fb)

BigSimmoand others added 4 commits August 27, 2026 20:35
CI's Static PR checks job failed because merging main (#2422) shifted
component adoption counts without regenerating the tracked snapshot.
Re-run npm run design-system:adoption:update to bring
docs/design-system/adoption-manifest.json and COMPONENTS.md back in
step.
@cursor

cursorBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_46e19f74-40a0-49d2-b64d-ac307dca55e2)

@BigSimmo
BigSimmo enabled auto-merge (squash) August 27, 2026 13:04
claudeand others added 2 commits August 27, 2026 13:15
This PR's Chip change unified the remove button's hit area to a fixed
min-h-tap regardless of wrap state, but two ui-v2-components.dom.test.tsx
assertions still expected the old h-full / min-h-5 h-full classes that
no longer apply to the button element. Update both to assert min-h-tap.
@BigSimmo
BigSimmo merged commit 5df4520 into mainAug 27, 2026
30 checks passed
@BigSimmo
BigSimmo deleted the claude/ds-h36-tap-floors branch August 27, 2026 13:29
BigSimmo pushed a commit that referenced this pull request Aug 27, 2026
Resolve conflicts in favour of main, which has since landed the same
design-system intent through the shared recipes and Button/PageHeader
adoption (PRs #2420, #2424, #2425, #2426):
- ui-primitives.tsx: main split the module into primitive-recipes/*; the
branch's compact-meta edits to `interactiveCompact` and
`tableMicroActionRow` are already present verbatim in recipes.ts.
- specifier compare/map/record/builder, differential-detail: main's
`primaryControl` / `Button` adoption carries the same `min-h-tap` floor
through `controlBase`, so the hand-rolled classes are superseded.
- formulation-builder: main's `fieldControlPlain` recipe supersedes the
hand-rolled textarea classes.
- pathways-screen: main's therapy-pathways redesign (#2413) already
removed the arbitrary spacing literals this branch was ratcheting.
Regenerate the contract baseline against the merged tree.
Sign up for freeto 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

@BigSimmo@claude