ALT[CMD]-TAB

[lumpidu]

I am often using just the keyboard for switching between the browser and terminal. Often i combination with C&P.

When navigating away from the HostedGPT window via CMD-TAB to my terminal, pasting some code, CMD-V, selecting text, CMD-C, navigating back CMD-TAB and then trying to paste the code CMD-V, the text window doesn't have the input focus anymore, so I need to constantly move the mouse to the text input field.

This annoys me every time. Is there a reason, why the focus isn't always inside the input field of a current conversation ?

[krschacht]

I think it should be. Is the text input properly focused when you Cmd+Tab away but then it’s lost it when you Cmd+Tab back? Or is it not focused properly in the first place?

Also, there is a shortcut to focus the input: / But I still agree with you that it should not lose focus. However, I’m wondering if this is an OS behavior rather than an app issue.

[lumpidu]

Yes the input field is already properly focused before switching away and back again. I am on MacOS / Firefox. Happens also on Safari.

[lumpidu]

And if I press the "/" key (which on my German keyboard is SHIFT-7), Firefox activates the search field ...

[krschacht]

I tested google.com and notably it behaves the way you want it to. AI is telling me that the HostedGPT app is behaving the default way all browsers behave and there needs to be some custom handling to restore focus into a specific text input.

I just did this PR #608 to handle restoring focus. I'll merge it in shortly.

Separately, it sounds like the "/" keyboard shortcut is not working properly for you. I did not investigate that. I'm not sure if it's an issue specific to Firefox or specific to German keyboards.

[lumpidu]

This is not browser-specific: the same behaviour exists in Chrome, Safari. If I switch the keyboard layout to English US, it works as expected. You could probably reproduce it, if you add the German keyboard layout and use SHIFT-7 for "/".

I have a similar problem in my Jetbrains IDE, where the back-/forward navigation is set to "CMD-[" "CMD-]", which never works on the German Keyboard. But I am sure, this is not related to German keyboards alone ...

[lumpidu]

As a total JS noop, just wild guessing:

Would it be possible to use the keypress event instead of keydown and then use sth. like the following:

var unicodeCharCode = e.charCode;
var userInput = String.fromCharCode(unicodeCharCode);

AI's opinion suggests that even just switching the event from keydown to keypress would solve the problem.