Ctrl + Shift + x only opens but does not toggle closed extensions

[drankinatty]

Describe the bug Going though New Features on 1.85 looking at New Tooltips, the Ctrl + shift + x to toggle extesions - will only open the extensions window, but fails to toggle it closed on subsequent Ctrl + Shift + x.

Please confirm that this problem is VSCodium-specific

• [ ] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

No clue - I don't have MS VScode

Please confirm that the issue/resolution isn't already documented

• [ x ] I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior:

1. open VSCodium
2. Click Ctrl + shift +x to open the extensions pane
3. Now Click Ctrl + shift + x to toggle the extension pane closed
4. It fails to toggle close

Expected behavior I really appreciate the ability to use key-combinations to access the various panels, that is good interface design, and prevents having to grab the mouse, point, click and then reposition your hands on the keyboard. However, to be useful, a shortcut must Toggle the view open and then toggle it back closed when the shortcut is given a second time.

If the shortcut only opens extensions, but fails to close it when given a second time, then all the efficiency and good design that prevents having to reposition your hands on the keyboard is lost.

Screenshots If applicable, add screenshots to help explain your problem. N/A

Desktop (please complete the following information):

• OS: openSUSE Leap 15.4
• Architecture x64
• Version [e.g. 1.85.1]
• App Manager RPM
• Sandboxed nope

Additional context None, pretty self-expanatory.

[github-actions[bot]]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

[github-actions[bot]]

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.