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

Active app unable to receive keystrokes after Scrolla on Spotlight #11

Open
jannis-baum opened this issue Nov 25, 2022 · 9 comments
Open

Comments

@jannis-baum
Copy link

With Safari on this issue active, if I

  1. Press cmd+space to open Spotlight
  2. Activate Scrolla
  3. Deactivate Scrolla with its hotkey
  4. Press cmd+space to close Spotlight

Safari looks like it is focussed but can't receive any keystrokes anymore. Mouse works but whatever key or key-combination I press (cmd-q and the like included), my computer always makes the annoying "you can't do this" sound we talked about earlier. Only way to fix it from there seems to be to switch focus to another app and back to Safari.


Might be that this will already get resolved with the new release regarding #3?

@jannis-baum
Copy link
Author

Still the same in a3

@godbout
Copy link
Owner

godbout commented Nov 25, 2022

this seems to be an issue with Spotlight. you can replace Scrolla by Wooshy, Alfred, or any other app that brings a non activating panel and you'll get the same results. i pay attention that kV, Wooshy and Scrolla don't leave any window/active app dangling (updates coming for kV and Wooshy to handle this better). if it's kV/Wooshy/Scrolla, pressing command , will bring the Settings. in this case it does nothing. Alfred has a similar issue in some cases, but brings its Preferences. it's quite common for apps not to take care of this properly. it's weird. most of them, when you quit their Settings, the app is still dangling around.

this is definitely gonna be annoying for Spotlight's users... would need an Apple feedback that will probably not change anything.

@godbout
Copy link
Owner

godbout commented Nov 25, 2022

i've just tried with Things 3 that also has a non activating panel that also doesn't disappear when you call other non activating panels. same thing happens. so maybe not a Spotlight thing. maybe a macOS thing... kV/Ws/Sl for Linux? ☹️

@godbout
Copy link
Owner

godbout commented Dec 2, 2022

closing this one because this is not related to Scrolla, but to macOS and Non Activating Panels that don't disappear when another Non Activating Panels shows up. should rather be sending a FB to Apple.

@godbout
Copy link
Owner

godbout commented Dec 2, 2022

actually will close on the FB is done.

@godbout
Copy link
Owner

godbout commented Dec 22, 2024

i've just tried with Things 3 that also has a non activating panel that also doesn't disappear when you call other non activating panels. same thing happens. so maybe not a Spotlight thing. maybe a macOS thing... kV/Ws/Sl for Linux? ☹️

tried again with Things 3 and now it works fine. so it's definitely an issue with Spotlight.

@godbout
Copy link
Owner

godbout commented Dec 22, 2024

tried again with Things 3 and now it works fine. so it's definitely an issue with Spotlight.

actually not fully.

so it seems that what happens is that with those Non Activating Panels, macOS is screwing up who's the next responder. the same behavior happens when you use Alfred, Homerow or some other apps instead of Ws/Sl 🤔️

the only two things i'm thinking about here is:

  1. write a FB to Apple, but kinda hard to explain what's going on
  2. when leaving Ws/Sl, checking what's the workspace app (show in the menu bar) and force-activating it? doubt that would work but could try

@godbout
Copy link
Owner

godbout commented Dec 22, 2024

  1. when leaving Ws/Sl, checking what's the workspace app (show in the menu bar) and force-activating it? doubt that would work but could try

tried. doesn't work. pretty sure i had tried before. so what's next is really to report to Apple 😴️

@godbout
Copy link
Owner

godbout commented Dec 24, 2024

FB to Apple done: feedback-assistant/reports#589

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

No branches or pull requests

2 participants