Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add shortcut for dev tools #5465

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SethFalco
Copy link
Contributor

@SethFalco SethFalco commented May 20, 2023

When running Tutanota from source, one thing that always bothered me is that I couldn't do CTRL + SHIFT + I to open dev tools. ^-^'

This is a standard shortcut available in both Firefox and Chromium-based browsers.

In all the Electron applications that I've used which include access to dev tools on production builds, CTRL + SHIFT + I was the supported method, which is where my habit of using that instead of F12 came from anyway:

  • Element, specifically allows CTRL + SHIFT + I but not F12 for some reason. πŸ€”
  • Discord, when I last used it, allowed CTRL + SHIFT + I but not F12.

Mind if we add this as a supported shortcut? ^-^'

References

You can open the Firefox Developer Tools from the menu by selecting Tools > Web Developer > Web Developer Tools or use the keyboard shortcut Ctrl + Shift + I or F12 on Windows and Linux, or Cmd + Opt + I on macOS.

β€” https://firefox-source-docs.mozilla.org/devtools-user/index.html#the-core-tools

Action Mac Windows / Linux
Open whatever panel you used last Command+Option+I F12 or Control+Shift+I

β€” https://developer.chrome.com/docs/devtools/shortcuts/#open

Firefox, Ctrl + Shift + I: Toggle developer tools
Microsoft Edge (Chromium), Ctrl + Shift + I: Open Developer Tools
Vivaldi, Ctrl + Shift + I: Developer tools
Discord, Ctrl + Shift + I: Open developer console

β€” https://defkey.com/what-means/ctrl-shift-i#general

@ganthern
Copy link
Contributor

thanks for your initiative again!

We'd have to think about it because we're already running into conflicts with shortcuts that we'd like to use but can't because they're used by the browser. We're not sure yet if just giving the desktop app more freedom here vs keeping it and the browser version as close as possible is the best approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants