Conflicting Keyboard Shortcuts

[bsget]

Describe the bug The hotkey Ctrl + Left Arrow will toggle the side panel which conflicts with many OS's reserved shortcut for moving back one word. So when you are entering a url or variable and you press Ctrl + Left Arrow to go back word by word the side panel constantly toggles. The toggling of the panel should be bound to a non-reserved shortcut to not conflict with OS's reserved shortcuts.

To Reproduce Steps to reproduce the behavior:

1. Create a new request
2. Enter a long URL (eg. https://www.example.com/test/example-of-a-long-url)
3. Put cursor at end of URL
4. Press Ctrl + Left Arrow to go back word by word.
5. See error (the side panel toggling with each press of Ctrl + Left Arrow)

Expected behavior Ctrl + Left Arrow should do nothing within firecamp

Firecamp has the shortcut Ctrl + Left Arrow bound to toggle the side panel open/closed. This functionality should be bound to something different within firecamp as Ctrl + Left Arrow is a reserved shortcut within most OS's. OS's handle Ctrl + Left Arrow to go back one word.

Solution Remap toggling the side panel to a different hotkey other than Ctrl + Left Arrow (ensure it is not a reserved hotkey)

Platform

• Type: Desktop
• OS: Ubuntu 18.04 and Windows 10
• Firecamp Version: 1.4.7

Additional context No OS reserved shortcuts should be used within applications. The reserved shortcuts for the most common OS's are as follows:

• Mac OS: https://developer.apple.com/design/human-interface-guidelines/macos/user-interaction/keyboard/#keyboard-shortcuts
• Windows: https://support.microsoft.com/en-us/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec
• Unix: https://www.computerhope.com/ushort.htm

[welcome[bot]]

Welcome to the Firecamp! Thanks and congrats for opening your very first issue in Firecamp. Join the Discord community here https://discord.gg/8hRaqhK Hope you have a great time here :)

[Nishchit14]

Thank you @bsget for sharing the context. We'll improve the experience based on your feedback.

[bsget]

In testing the canary version it seems the redesign has fixed this issue. I am going to close this issue as the in-development version no longer has this bug.