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
Switching not working on Big Sur #996
Comments
Can you please clarify what you mean exactly by "The switching is not working"? A video would help understand your problem a lot |
Not sure if I'm experiencing the same issue as OP, but after updating to MacOS 11.4 and FireFox 89.0.1, it seems that switching to FireFox doesn't work but switching to everything else I use does work. When attempting to switch to FireFox, simply nothing happens. |
@csuich2 does switching work with previous versions of Firefox? It sounds like it's an issue either with that latest Firefox release or with Big Sur. |
Everything was working fine before I updated this morning. FireFox updated due to being restarted, so I didn't get a chance to tell whether it was the Big Sur (11.4) or FireFox update that broke it. |
You could downgrade Firefox to test if AltTab works with the previous version |
After a couple days of experimentation, I've found that it isn't just FireFox. I've also seen issues switching to just about every application I use. Interestingly, thing seem better today, but I don't believe anything was updated today or yesterday. I'll update again in a few days. |
I meant the windows switching wasn't working properly. But today seems better. No issues from my side today. |
I'm still seeing the issue intermittently on applications like VS Code, Insomnia and FireFox. |
Now, the issue is affecting Spotify and Obsidian... |
Hey there,
The most weird thing is that this behavior appears and disappears around reboots - I don't experience it all the time. AltTab version 6.22.1 |
@vitalihs i'm wondering if your VSCodium issue is not the same that was discussed and solved here: #992 (comment)
It seems to suggest these apps introduced the issue recently. AltTab hasn't released related changes in the past months, so it can't suddenly break This ticket appears to me like a collection of apps that have accessibility bugs that are revealed by AltTab but most likely not an issue of AltTab itself |
Thanks for pointing this issue! I'm working with VSCodium and its version is 1.58, I have no idea if there's parity between VSCode and VSCodium versions, but I'll assume there is. I'll try to downgrade VSCodium to check if that's the case... I'll write you back if I find something |
Hey @lwouis, I just downgraded vscodium to 1.57.1 and it seems AltTab works as expected now. Vitali |
The Electron apps is clearly a bug on their side. I can't think of a workaround to implement in AltTab because these apps are claiming focus after a switch (also without AltTab installed, see the video here). This ticket here is mixing many apps and many symptoms. It's hard to work on such vague messages. It would help if people shared clear steps to reproduce, video of the issue in motion, etc. So to recap:
|
I see, thank you for explaining the details lwouis. |
is there an upstream electron issue we can follow? |
I think this is it for anyone wondering electron/electron#29857 |
Here are some steps to repro that are fairly reliable for me:
So cycling from firefox to vscode works fine, cycling from vscode to firefox does not work reliably. Workaround: |
This sounded like the Electron/VSCode bug we already covered, but then you added:
So it's a particular issue between VSCode and Firefox? That's extremely specific. You're saying that:
That sounds so particular. Could you please share a video so we can see how it looks in motion? |
ok nevermind I narrowed down the behavior a bit more generally
but at this point I think it's just the electron bug so I will wait until the fixes land in vs code and try again |
i encounter the same problem , switch between Firefox and Obsidian not work. |
Maybe fixed in v6.32.0? |
This issue was opened by a bot after a user submitted feedback through the in-app form.
From: luiscachog@gmail.com
Message:
Debug profile
The text was updated successfully, but these errors were encountered: