Keyboard shortcuts: Fix Ctrl+G and other intermittently-firing shortcuts on Win/Linux #2705
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix
Fixes #2420
Some keyboard shortcuts were silently failing on Win/Linux builds. After adding logging and debugging this I was able to determine that the
if focusedWindow
check was failing. I still don't know exactly why, as this works on OSX.Changing it to explicitly check if the
focusedWindow
isundefined
seems to fix the issue in my testing. I have only tested this on Windows, not Linux.After some research, I think it would be safe to remove this guard entirely. The documentation does state that it can be
undefined
, but only in the case where no window is open, which only applies to OSX. (confirmed by a comment here)Test
Release
Fixed a bug that caused Ctrl+G and some other shortcuts to fail on Windows/Linux builds