Disabling a keybind disables it system wide, not just the browser
63 views
Skip to first unread message
Kiingy ಠ_ಠ
Apr 18, 2024, 9:01:54 PM4/18/24
to AutoControl
Hi,
I'm using this extension to disable the F11 and F12 keybinds on chrome, it works however it also disables that keybind for the entire system while the browser is in focus..
For example;
I use F12 as discords push to talk keybind, so I need to disable that bind in chrome so the developer tools window doesn't pop up, but discord still needs to react to it. In this case, the extension disables that keybind everywhere.
I'm using this extension to disable the F11 and F12 keybinds on chrome, it works however it also disables that keybind for the entire system while the browser is in focus..
For example;
I use F12 as discords push to talk keybind, so I need to disable that bind in chrome so the developer tools window doesn't pop up, but discord still needs to react to it. In this case, the extension disables that keybind everywhere.
Is there a setting to allow for other applications to still get keybinds that have been disabled in autocontrol?
AutoControl support
Apr 19, 2024, 12:01:20 AM4/19/24
to AutoControl
You need the keystroke to be detected by the webpage but not by the browser. To achieve that you have to override the key and make it inject the same key from inside the webpage, as shown below.
Kiingy ಠ_ಠ
Apr 20, 2024, 2:33:33 AM4/20/24
to AutoControl
Sorry I should have mentioned this is using the discord desktop application, not the web version.
When unbinding the F12 key in chrome, if chrome is in focus, the desktop discord client doesn't get the F12 event either, it seems to disable the key system wide.
When unbinding the F12 key in chrome, if chrome is in focus, the desktop discord client doesn't get the F12 event either, it seems to disable the key system wide.
AutoControl support
Apr 21, 2024, 2:04:20 PM4/21/24
to AutoControl
If the Discord app is listening for system-wide keyboard shortcuts, then it will be in conflict with other apps that also do the same, such as AutoControl.
In this situation, an app may or may not see a given keystroke depending on which of the 2 apps received the keystroke first.
In order to work around this cat-and-mouse problem, you have to configure Discord to accept a second shortcut for the same action as F12; for example CTRL+F12.
Then, in AutoControl you must do this:
In this situation, an app may or may not see a given keystroke depending on which of the 2 apps received the keystroke first.
In order to work around this cat-and-mouse problem, you have to configure Discord to accept a second shortcut for the same action as F12; for example CTRL+F12.
Then, in AutoControl you must do this:
This way, when Chrome is focused, F12 will be overridden and Discord will see a CTRL+F12 combination.
When Chrome is not focused, F12 will not be overridden and therefore Discord will see the keystroke and react to it.
If the Discord app doesn't allow you to specify 2 keyboard shortcuts for the same action, then you can override F12 at all times (i.e. when Chrome is focused and unfocused) as follows:
And then configure Discord to use only CTRL+F12. This way, pressing F12 will always trigger a CTRL+F12 combination which Discord will detect.
Reply all
Reply to author
Forward
0 new messages