Obsidian window consumes any hotkey input even if it not bound

Steps to reproduce

  • have an external program that has global shortcut available(for example I have discord cumstom shortcut to mute alt+shift+a)
  • Open obsidian and have it’s window active
  • Use the shortcut

Did you follow the troubleshooting guide? [Y/N]

Yes, tested, repeatable in sandbox Vault

Expected result

Expected other programs to react for the global shortcuts, if Obsidian does not have this shortcut bound.

Actual result

Input get consumed and external programs does not react to global hotkeys

Environment

SYSTEM INFO:
Obsidian version: v1.6.7
Installer version: v1.6.7
Operating system: Windows 11 Pro 10.0.22635
Login status: not logged in
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none


Additional information

This is also happens with windows feature enabled Use the print screen key to open screen capture : instead of opening screen capture system just does a screenshot of the screen.

I can’t reproduce this.

It does not repeat itself even with discord example?
I just tested it on 1.7.4 - and had same result in sandbox vault even with all core plugins disabled.
While Obsidian window is selected discord system-wide hotkey for mute does not work. And when I change selected window to anything else - it start working instantly. I may be wrong, but my best guess - Obsidian looks into key chord pressed and if it is not found it not passes it as “unhandled” to system. Or it may be Vim feature catching input, even when disabled

SYSTEM INFO:
	Obsidian version: v1.7.4
	Installer version: v1.7.4
	Operating system: Windows 11 Pro 10.0.22635
	Login status: logged in
	Language: en
	Catalyst license: none
	Insider build toggle: off
	Live preview: on
	Base theme: adapt to system
	Community theme: none
	Snippets enabled: 0
	Restricted mode: on

RECOMMENDATIONS:
	none

If I can provide more information to help sort this out - I would be glad to provide this.

Just updated to version 1.7.5 and this issue is fixed for me

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.