jpmschweitzerandClaude
ae8d774529
test / unit + widget + golden + a11y (push) Failing after 31s
test / integration_test (xvfb) (push) Has been skipped
test / bundle smoke (xvfb 5s) (push) Has been skipped
test / daemon subprocess + web WASM smoke (push) Has been skipped
test / dart doc (lib API) (push) Failing after 1m0s
Previously every PointerScrollEvent fell straight to PgUp/PgDown keyInput as a "universal scroll" workaround. That kept plain shells scrolling but starved vim mouse=a / htop / less of the wheel events they expect. Now `_onPointerSignal` checks `terminal.mouseMode.reportScroll` first (the cascade of mouse handlers cares about this flag). If the inner program declared ?1000h / ?1002h / ?1003h (optionally +?1006h SGR), the wheel forwards as `wheelUp` / `wheelDown` button events through the existing `renderTerminal.mouseEvent` path. Plain shells stay on PgUp/PgDown because their mouse mode is `none` — the existing test for that path keeps passing unchanged. Click + drag forwarding through the gesture handler was already wired (renderTerminal.mouseEvent for taps), so T-74's acceptance list is met by this scroll fix alone. Co-Authored-By: Claude <noreply@anthropic.com>