mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-10-23 08:07:35 -06:00
[GH-ISSUE #1923] Settings window opens behind other windows when clicked from the menu bar (macOS 27.0.1) #1335
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
information
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
github-starred/MonitorControl#1335
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JamesGeiger on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1923
Before opening the issue, have you...?
Describe the bug
When I click "Settings…" in the MonitorControl menu bar menu, the Settings window opens but does not come to the front. It stays behind other app windows, so it looks like nothing happened until I find it manually (Cmd-Tab / Mission Control).
MonitorControl v4.4.0, macOS 27.0.1, M5 MacBook Pro.
Steps to reproduce
Expected behavior
The Settings window should open in front of all other windows and take focus, as it does for other menu bar apps.
Anything else?
Possible cause (from reading the v4.4.0 source, not verified on macOS 27): the app is a menu-bar-only app (LSUIElement = true), and "Settings…" calls settingsWindowController.show() from sindresorhus/Settings. That calls NSApp.activate() on macOS 14+, and activation there is cooperative, so the system may ignore the request when the menu-bar app isn't already frontmost.
Environment Information (please complete the following information)
@waydabber commented on GitHub (Oct 14, 2026):
For some reason I can't reproduce this issue, at least on macOS 27.2 (latest beta).