Symptom. The base .icon-btn is already a tight 38×38px, but .row-actions .icon-btn (the rename/pin/archive menu trigger "⋮" and the delete "✕" on every session row in SessionDrawer) is explicitly shrunk further to 30×30px.
Why it matters. 30px is well under the widely-used 44×44px minimum touch target (WCAG 2.5.5, iOS HIG), on exactly the kind of small, closely-packed row controls most prone to mis-taps — and these are destructive/state-changing actions (delete, archive).
Source. mobile/src/ui/styles/chat.css:1495 (.row-actions .icon-btn { width: 30px; height: 30px; font-size: 13px; opacity: 0.65; }), vs. the base .weft-session .icon-btn { width: 38px; height: 38px; } at chat.css:129.
Direction. Increase the tappable hit area to at least 44×44px (padding can keep the visual glyph small) for .row-actions .icon-btn, especially the delete/menu triggers.
Symptom. The base
.icon-btnis already a tight 38×38px, but.row-actions .icon-btn(the rename/pin/archive menu trigger "⋮" and the delete "✕" on every session row inSessionDrawer) is explicitly shrunk further to 30×30px.Why it matters. 30px is well under the widely-used 44×44px minimum touch target (WCAG 2.5.5, iOS HIG), on exactly the kind of small, closely-packed row controls most prone to mis-taps — and these are destructive/state-changing actions (delete, archive).
Source.
mobile/src/ui/styles/chat.css:1495(.row-actions .icon-btn { width: 30px; height: 30px; font-size: 13px; opacity: 0.65; }), vs. the base.weft-session .icon-btn { width: 38px; height: 38px; }atchat.css:129.Direction. Increase the tappable hit area to at least 44×44px (padding can keep the visual glyph small) for
.row-actions .icon-btn, especially the delete/menu triggers.