Skip to content
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

Closed
willmcgugan opened this issue Aug 30, 2023 · 7 comments
Closed

Glitch with input #3205

willmcgugan opened this issue Aug 30, 2023 · 7 comments
Labels
Can not reproduce The issue couldn't be reproduced

Comments

@willmcgugan
Copy link
Collaborator

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.

@rodrigogiraoserrao
Copy link
Contributor

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.”.

@davep
Copy link
Contributor

davep commented Aug 30, 2023

I'm also failing to reproduce this with terminal.app v2.13 (447) on macOS 13.5. I've also tried with a Textual app running under screen and tmux within terminal.app and still can't get the same effect.

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).

@willmcgugan
Copy link
Collaborator Author

Oh well. Let's park this until we have more information.

@rodrigogiraoserrao rodrigogiraoserrao added the Can not reproduce The issue couldn't be reproduced label Oct 2, 2023
@darrenburns
Copy link
Member

Possibly related? #3647

@willmcgugan
Copy link
Collaborator Author

Still can't reproduce. Closing, assume fixed.

For future reference, never post Discord links because they expire.

Copy link

Don't forget to star the repository!

Follow @textualizeio for Textual updates.

@davep
Copy link
Contributor

davep commented Jun 17, 2024

FWIW, the now-missing recording is this:

recording

(found by searching Discord for the quote @rodrigogiraoserrao posted from the original discussion).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Can not reproduce The issue couldn't be reproduced
Projects
None yet
Development

No branches or pull requests

4 participants