Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2.7 KiB
FAIL
-
crates/ely-lok/src/view/turn.rs:41 — Logical scroll lines are counted as physical wheel notches. Windows multiplies each notch by the system scroll-line setting (
vendor/gpui-pre-windows/src/events.rs:589); with three lines configured, one downward notch producesLines(0, -3). Replaying that event through ElyShow and the rebuilt LOK worker moved from slide 1 to slide 4, rather than slide 2 (.work/R6.13-r1/probe-explicit.log). The pinned Linux X11 backend also uses three lines per notch. Normalize platform wheel units before counting slide changes, and cover realistic platform deltas; the existing tests only exercise unit notches. -
crates/ely-lok/src/view/turn.rs:37 — The line-delta branch never applies the one-turn-per-gesture limit, but the pinned GPUI X11 backend also represents smooth touchpad scrolling as
ScrollDelta::Lines(gpui-pre-linux-0.3.8,x11/client.rs,get_scroll_delta_and_update_stateandmake_scroll_wheel_event). Replaying ten consecutive-0.4line deltas in one UI update through ElyShow/LOK moved from slide 1 to slide 5 instead of slide 2 (.work/R6.13-r1/probe-extra.log). Preserve the distinction between discrete wheel steps and smooth XInput gestures in the input adapter, and apply gesture limiting to the latter; clamping each event individually would still turn repeatedly during one swipe. -
crates/ely-lok/src/view/turn.rs:48 — A 250 ms pause resets
spenteven when the platform reports continuation of the same gesture. With a fitted deck, aStartedevent of -60 pixels turns one slide; keeping fingers down, pausing 300 ms, then sending aMovedevent of -60 pixels turns another. This reproduced through ElyShow/LOK with slide index 2 instead of 1 (.work/R6.13-r1/probe-explicit.log). Track explicit gesture lifetime when phases are available; elapsed time must not reopen an explicitly ongoing gesture. Reserve timeout inference for streams without gesture boundaries and test continuation after a pause. -
crates/ely-lok/src/view/turn.rs:80 — The arrow-key decision uses the last selection callback without accounting for earlier queued input. On a title slide, press Tab to select its placeholder and Down before the worker's selection callback arrives: Down emits
Turn, so the queued Tab selects the object and the following part change leaves the slide instead of moving that object. The integration probe changed slide index 0 to 1; its control case, waiting for Tab's selection before Down, stayed on slide 0 (.work/R6.13-r1/probe-extra.log). Resolve the arrow's action against the selection/editing state after preceding inputs and their callbacks have landed, while preserving input order, and add this queued-input regression.