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

Quick-switching between services does not focus text input #1255

Open
jsanford8 opened this Issue Feb 3, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@jsanford8
Copy link

jsanford8 commented Feb 3, 2019

Describe the bug
Since the beta 23 upgrade, after utilizing quick switch (cmd+num) to switch between services, the keyboard is not focused on the new service. Instead, it is still focused on the previous service.

For instance, if you are on Slack, and you CMD+2 to a new service (say gmail), and try to use keyboard shortcuts (j/k to move up/down the email list), nothing will happen. Moving back to Slack, you'll see each keyboard input shown in the text field (i.e. a bunch of j's and k's).

This did not happen prior to beta-23

To Reproduce
Steps to reproduce the behavior:
See above. Go to Slack within Franz. Quick Switch (cmd+num) to gmail. Press j or k to navigate message list.

Expected behavior
j and k should navigate through the message list. It does not. Instead, each j and k input (and all keyboard input) is in the active chat window within the Slack service.

Screenshots
N/A

Desktop (please complete the following information):

  • OS: OSX
  • Browser Desktop... so Chrome?
  • Version 5.0.0 beta 23

Additional context
Again, this never happened until beta 23, which seems to have broken a lot of things. Franz has been great, but these updates breaking core existing functionality borderline make this not worth using,

@adlk

This comment has been minimized.

Copy link
Contributor

adlk commented Feb 3, 2019

Thanks for reporting.

Again, this never happened until beta 23, which seems to have broken a lot of things. Franz has been great, but these updates breaking core existing functionality borderline make this not worth using,

We updated electron from chromium 61 to 69 so in theory a lot could have gone wrong. If a lot of core functionality isn't working then please report it.

Issue to watch: electron/electron#15718

@adlk adlk added the bug label Feb 3, 2019

adlk added a commit that referenced this issue Feb 3, 2019

@jsanford8

This comment has been minimized.

Copy link
Author

jsanford8 commented Feb 3, 2019

So far the biggest I've seen are the input focus not being correct after quick switching, and then this one: #1252

@jsanford8

This comment has been minimized.

Copy link
Author

jsanford8 commented Feb 3, 2019

Also, I just tested with beta24 and this seems to be resolved now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment