You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(css): raise the remaining 44 px controls to the 48 px touch-target minimum #235
The house rule from Kpa-clawbot#2052 sets a 48 px minimum touch target, and #229 raised .fav-star to 48 px. public/style.css still sizes several controls at 44 px. None of them are in test-touch-targets.js or in the Kpa-clawbot#2052 tests:
.theme-toggle
.modal-close / .ch-modal-close (inside a media block)
.ch-back-btn
.ch-avatar.ch-tappable
.suggest-claim
.detail-back-btn / .filter-toggle-btn (inside a media block)
test-issue-2052-touch-target-e2e.js itself notes that other controls "are outside Kpa-clawbot#2052 and still 44". This list comes from the #229 review.
Proposed fix
Raise each control to at least 48×48 px, using the existing CSS variables or tokens. No hardcoded colours.
Check the layout at 390 px and on desktop wherever each control appears, with no horizontal page overflow. The channel header, the modals, the nodes detail and the suggest dialog are the likely tight spots.
Relates to #189, #229
Problem
The house rule from Kpa-clawbot#2052 sets a 48 px minimum touch target, and #229 raised
.fav-starto 48 px.public/style.cssstill sizes several controls at 44 px. None of them are intest-touch-targets.jsor in the Kpa-clawbot#2052 tests:.theme-toggle.modal-close/.ch-modal-close(inside a media block).ch-back-btn.ch-avatar.ch-tappable.suggest-claim.detail-back-btn/.filter-toggle-btn(inside a media block)test-issue-2052-touch-target-e2e.jsitself notes that other controls "are outside Kpa-clawbot#2052 and still 44". This list comes from the #229 review.Proposed fix
test-touch-targets.js, or to the style.css declares .nav-btn and .ch-icon-btn at both 48px and 44px Kpa-clawbot/CoreScope#2052 E2E, so that a regression to 44 px fails.Acceptance