Mac client doesn't fully return focus to previously focused program
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I have Keybase installed on my Mac. I click on the Keybase icon on the right side of my menu bar, then click to open chat, the chat windows pops up and I can chat to my heart's content. In the menu, next to the Apple menu, it properly says "Keybase" as the active/focused program. Then, I close the window with "quit" (which isn't really intuitive, since I'm just closing the window, not quitting the app, but just closing the Window leaves the icon in the Dock). The application name next to the Apple menu in the menu bar goes back to whatever I was using before (for instance, Firefox), however (and this is the bug), that program (Firefox, in this case) is not actually focused. I still have to click on the program to fully return focus before I can continue interacting with it.
While I was reproducing the issue to type up this report, I noticed another way to trigger this loss of program focus. Simply click the Keybase menu item to open it, then click it again to close it. Just as described above, the active application in the menu will change from Firefox (in my case) to Keybase back to Firefox, but I have to click my Firefox window to really focus it before I can continue typing into this text box.
Hopefully, my description and instructions make sense. I'll be happy to clarify or answer any questions about it.
Edit: there's a visual indicator to show this happening. While a Firefox window is inactive or not focused the back/forward buttons (if there's history for the selected tab) and any extension icons are greyed out. So, if you click on the Keybase menu to open it, the macOS menu shows "Keybase" and the Firefox icons greys out. If you then click the Keybase menu again to close it, the macOS menu shoes "Firefox" again, but the icons are still greyed out because the window is not actually focused/active.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Reproduce the focus loss by opening and closing the Keybase menu or chat window on macOS, then trace the Mac client's focus restoration behavior; done means the previously focused application window accepts input immediately after Keybase closes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100