Repository navigation
core: one button with a 44-point touch hit area, redone cleanly (K-1, replaces PR #991) - #1007
fizzy-linux[bot] wants to merge 2 commits into
Conversation
Agent-Team: linux Worker: codex
PM note: how this PR will be handledWhat it is for: linux: work-715 Rules that apply: touches build scripts. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Author's turn What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Rules that apply: touches build scripts. Reviews at the current commit (
2 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/716#issuecomment-6499713351 (4 findings answered) Updated 2026-10-29 15:21 UTC by the PM. This comment is edited in place. |
Agent-Team: linux Worker: codex
|
Closed by the PM (2026-11-01): it no longer merges after the touch chain and rework runs made no change. Redone on today's main as https://github.com/fizzyedit/work/issues/893. The branch stays for reference. |
Part of fizzyedit/work#715
Rework: work#731
In plain words
This follow-up restores two safety checks that were accidentally removed from the code checker. It also trims unused button code while keeping the larger touch target and existing button behavior.
What you will notice
Nothing visible: internal review fixes. The settings Restart button keeps its 44-point touch target.
How this serves fizzy
Goal: phone touch targets, with code quality and evidence preserved so small buttons remain easier to tap without sacrificing existing checks.
Goal
Answer windows/claude F1–F4 on PR #1007 at afe32c6.
What changed and why
Restored the same-line suppression and exact-budget assertions verbatim from 9e74a09 (#988). Removed nine unused Button delegators and consolidated the callback ownership comments. Checked the pinned dvui source: ButtonWidget.processEvents delegates to the same clicked path, preserving keyboard activation, hover, pointer capture and touch-drag cancellation; F3 is declined with source evidence in FIXES.md.
How it was verified
See GATES.md for exact commands, step summaries and limitations. The restored lint tests exercise trailing-comment suppression and quiet reporting at an exact allowance. Existing Linux headless button tests cover touches outside the drawn rectangle and rejection of the same point with a mouse; this follow-up changes no visual behavior.
Not done / follow-ups
The harness must commit, push and post the single FIXES comment with its new head. No GitHub operations or git metadata writes were performed here. Repository lint has an existing Android sample violation, reproduced with the unchanged HEAD lint implementation. Sandbox socket failures are recorded in GATES.md.
Self-check: Q1 met for local fixes, with publication left to the harness; Q2 removes dead delegators and restores existing coverage; Q3 keep the existing click path, confirmed against pinned dvui; Q4 aligned with phone touch targets and evidence over opinion. Source delta: +9/-49 across two files. Risk: callers of the nine removed, unused wrapper methods must use inner; native and web builds passed.
Changes (7 files, +282/-6)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)