for example the 1-5 tabs clicking them with the mouse is wrong - the mouse seems to targert 5 large areas over the full width, whereas the tabs are shown left-aligned (which is correct, I like it that way). The mouse activities need to be better aligned with what is on the screen.
Also the scrolling via scroll wheel feels weird, it seems to be super fast. Not at all natural.
Maybe use computer use and ghostty to run the app in such a terminal and try the mouse clicking and wheeling that way?
for example the 1-5 tabs clicking them with the mouse is wrong - the mouse seems to targert 5 large areas over the full width, whereas the tabs are shown left-aligned (which is correct, I like it that way). The mouse activities need to be better aligned with what is on the screen.
Also the scrolling via scroll wheel feels weird, it seems to be super fast. Not at all natural.
Maybe use computer use and ghostty to run the app in such a terminal and try the mouse clicking and wheeling that way?
hugo
added this to the first feature complete release milestone 2026-08-03 19:24:46 +00:00
hugo
added the bugcritical labels 2026-08-03 19:24:46 +00:00
Live PTY run against the configured server with terminal-native SGR mouse events: rendered tab click switched to Issues, unused tab-bar space did nothing, list wheel moved one item, and Preview wheel moved one line
Computer Use was attempted with both Ghostty and Apple Terminal, but this environment's Computer Use runtime blocks both terminal bundle IDs before interaction
Release gotcha and gotcha-tui binaries built and installed to ~/.local/bin; installed TUI help invocation verified
This is a TUI-only change, so no iPhone build or deployment is required.
Implemented in `95526f8`.
- Replaced the five full-width tab hit regions with exact hit boxes matching Ratatui's left-aligned title, padding, and divider layout.
- Persisted Ratatui's actual rendered list offset so clicks select the row visibly under the pointer after scrolling.
- Reduced list wheel movement from three items to one item per event and scoped it to the list pane.
- Added one-line wheel scrolling for the Preview pane; wheel input outside the list and Preview no longer changes either pane.
- Added regression tests for exact tab hit boxes and scrolled-list row hit testing.
Verification:
- `cargo fmt --all -- --check`
- `RUSTFLAGS="-D warnings" cargo check --workspace --all-targets`
- `cargo clippy --workspace --all-targets -- -D warnings`
- `cargo test --workspace` (43 tests plus doc tests)
- Live PTY run against the configured server with terminal-native SGR mouse events: rendered tab click switched to Issues, unused tab-bar space did nothing, list wheel moved one item, and Preview wheel moved one line
- Computer Use was attempted with both Ghostty and Apple Terminal, but this environment's Computer Use runtime blocks both terminal bundle IDs before interaction
- Release `gotcha` and `gotcha-tui` binaries built and installed to `~/.local/bin`; installed TUI help invocation verified
This is a TUI-only change, so no iPhone build or deployment is required.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
for example the 1-5 tabs clicking them with the mouse is wrong - the mouse seems to targert 5 large areas over the full width, whereas the tabs are shown left-aligned (which is correct, I like it that way). The mouse activities need to be better aligned with what is on the screen.
Also the scrolling via scroll wheel feels weird, it seems to be super fast. Not at all natural.
Maybe use computer use and ghostty to run the app in such a terminal and try the mouse clicking and wheeling that way?
Implemented in
95526f8.Verification:
cargo fmt --all -- --checkRUSTFLAGS="-D warnings" cargo check --workspace --all-targetscargo clippy --workspace --all-targets -- -D warningscargo test --workspace(43 tests plus doc tests)gotchaandgotcha-tuibinaries built and installed to~/.local/bin; installed TUI help invocation verifiedThis is a TUI-only change, so no iPhone build or deployment is required.