[macOS 13] Command-` Keyboard Shortcut Does Not Work Properly
Categories
(Core :: Widget: Cocoa, defect, P2)
Tracking
()
People
(Reporter: haik, Unassigned)
References
(Blocks 1 open bug)
Details
On macOS 13 Beta 22A5295i and earlier Betas, the Command-` keyboard shortcut also known as command backtick does not work reliably. The command is meant to cycle focus through open non-minimized windows of the focused application. With Firefox, sometimes the shortcut works, but repeated presses eventually stop switching windows as if the feature is failing to cycle back to the first window.
I can reproduce a less significant version of this with some Apple macOS apps such as Safari and macOS Terminal, but for the those apps the problem only occurs on the first attempt to use the shortcut. Then the shortcut works reliably. The problem does not appear to occur in Chrome.
Tested on macOS 13 22A5295i on an Apple Silicon MacBook Pro M1 2020 13".
Updated•4 years ago
|
| Reporter | ||
Comment 1•4 years ago
|
||
Not knowing if this is a macOS or Firefox bug at this point, I've filed FB10870917 for the issue in Safari:
Description
Please describe the issue and what steps we can take to reproduce it:
The keyboard shortcut Command-` does not work reliably on macOS 13 Beta 22A5295i and earlier.With Safari, the command-` (command backtick) keyboard shortcut does not work reliably when Safari is first opened.
After opening Safari and creating a second window, using Command-` to switch between Safari Windows does not work reliably. Sometimes the first or second attempt fails, then after manually switching windows using the mouse to focus another window by clicking on it, then the shortcut starts working again.
| Reporter | ||
Comment 2•4 years ago
|
||
With macOS Beta 5 (22A5321d), the problem is no longer reproducible.
Comment 3•3 years ago
|
||
(In reply to Haik Aftandilian [:haik] from comment #2)
With macOS Beta 5 (22A5321d), the problem is no longer reproducible.
I am still able to reproduce this, but it affects all applications on my system. I found this workaround, but it doesn't work for me: https://discussions.apple.com/thread/252373102
Description
•