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

Tab skips twice when focused on text inputs #100

Closed
yilmaz08 opened this issue Aug 20, 2024 · 3 comments · Fixed by #101
Closed

Tab skips twice when focused on text inputs #100

yilmaz08 opened this issue Aug 20, 2024 · 3 comments · Fixed by #101

Comments

@yilmaz08
Copy link
Contributor

While editing the chat parameters I've realized that pressing Tab on "System" input or "Parameters" input was going to the next element twice. When on "System" input, it goes to "Parameters" and then quickly goes to "JSON output". It kind of looks like the key is pressed twice but it is not.
The same behaviour can be seen on the video attached.

I had no idea how to solve this so I am opening an issue.

bugreport-oterm.mp4

OS: Arch Linux
WM: bspwm
Terminal Emulator: alacritty
Installation: Manual (I had just cloned repo and installed packages to work on some stuff)

Thank you in advance!

@yilmaz08
Copy link
Contributor Author

The same thing happens on:

New Chat Page
Multiline prompt entry (it works perfectly on single line)

there must be something broken about multiline entries

@ggozad
Copy link
Owner

ggozad commented Aug 20, 2024

Yeah I've noticed the same. I could swear that it didn't always happen which probably means it's a bug in recent textual versions. Will look into it asap, thanks for the detailed report!

@ggozad
Copy link
Owner

ggozad commented Aug 20, 2024

Yeah I've noticed the same. I could swear that it didn't always happen which probably means it's a bug in recent textual versions. Will look into it asap, thanks for the detailed report!

I can confirm the issue is on our side, will fix.

ggozad added a commit that referenced this issue Aug 20, 2024
A patch was in place to allow theme handling for TextArea.
Since our changes have been properly pushed upstream it is no longer necessary.
Closes #100.
ggozad added a commit that referenced this issue Aug 20, 2024
A patch was in place to allow theme handling for TextArea.
Since our changes have been properly pushed upstream it is no longer necessary.
Closes #100.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants