-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glitch with input #3205
Comments
The OP wrote ”The potential bug occurred if I dragged and clicked my mouse across the input fields. I'm using the Mac Terminal app, it doesn't appear to happen in iTerm2.”. |
I'm also failing to reproduce this with Something to chase up with the developer might be exactly what pointing device they were working with (unlikely to be the issue, but it might be down to other inputs other than "drag" on, say, a trackball, or a mouse, or even something really fun like a SpaceNavigator -- yes I'm reaching here). |
Oh well. Let's park this until we have more information. |
Possibly related? #3647 |
Still can't reproduce. Closing, assume fixed. For future reference, never post Discord links because they expire. |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
FWIW, the now-missing recording is this: (found by searching Discord for the quote @rodrigogiraoserrao posted from the original discussion). |
Reported via textual web, but I suspect this is unrelated. On macOS Terminal.app inputs will show escape sequences for mouse movement.
https://cdn.discordapp.com/attachments/1140597677709611039/1146198894674456626/recording.gif
I suspect that Terminal.app is generating different sequences that Textual isn't picking up. If we log what the terminal is generating we should be able to figure it out.
First step would be an app and a single input. Hopefully this can reproduce it.
The text was updated successfully, but these errors were encountered: