Bug: iPad Magic keyboard trackpad and touch scrolling frequently stops working

[chrisintheshell]

I've been running into an issue where scrolling periodically stops working in an active terminal session. I'm mainly using my iPad with the Magic Keyboard trackpad, but when this occurs both the Magic Keyboard trackpad and touch scrolling stop working. This only affects the active terminal surface — other tabs continue to function properly.

I've had it happen both locally and remotely over SSH/Tmux.

I haven't been able to determine whats causing it, or if there is some kind of pattern. Let me know if there something I can provide you to debug.

I'm currently running version 1.0.4 build 73, but I've noticed this happening on the past few versions.

[kitknox]

I use the same combo on two different iPads frequently and haven't reproduced the problem yet. I have two different theories which could trigger this and implemented fixes for them. Hopefully after the next build you have better luck. If not I will sort out some better debug log instrumentation for this area.

[kitknox]

@chrisintheshell Has this been stable in the newer builds for you?

[chrisintheshell]

@kitknox so far so good — thank you!

[chrisintheshell]

@kitknox actually there is one thing I did notice, which is unrelated to the touch scrolling but related to copying text after scrolling. When trying to select text when doing a press and drag, I noticed that the magnified text box does some kind of movement reset when dragging beyond the middle of the terminal surface. The magnified text box resets (moves backwards) positionally when hitting the middle of the terminal surface, which is visually awkward as your eyes end up having to track back.

I suspect this was intended to prevent the magnified box from hitting the edge of the terminal surface before you finish selecting text. I think it would be better if the magnified box does this when getting close to the edge instead of the middle of the surface.

[kitknox]

@chrisintheshell Yes that was the reason it was doing this. I initially changed the offsets but it's still jarring. Refactored to be like the native control where no jump is required at all.