mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Consider getting rid of the "suppression" mechanism (global shortcuts) #2240
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#2240
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @davidebeatrici on GitHub (Jun 4, 2021).
"Suppression" means preventing other applications from receiving the input message.
#4941 removed support for the feature on Windows because the API we're now using doesn't allow to filter input.
The main reason for that is performance: the operating system doesn't have to wait until a response is returned before passing the input message to other applications.
macOS is now the only platform we support the feature on:
github.com/mumble-voip/mumble@4fab1880e1/src/mumble/GlobalShortcut_macx.mm (L149-L154)github.com/mumble-voip/mumble@4fab1880e1/src/mumble/GlobalShortcut_macx.mm (L476-L478)In order to work it requires the user to grant Mumble "accessibility" permissions:
macOS 10.15 (Catalina) introduced a new privacy category called "Input Monitoring", as explained at WWDC 2019:
https://user-images.githubusercontent.com/5897523/120877430-bb2de900-c5b6-11eb-843c-f3a9fe0bd366.mp4
By specifying that we only want to listen for input and don't filter it, we wouldn't need accessibility permissions anymore.
@Kissaki commented on GitHub (Jun 5, 2021):
I think suppression can be a useful feature, but I don’t think keeping the functionality around just for macOS is worth it, especially with the requirement issues you lay out here.
@Kissaki commented on GitHub (Jun 5, 2021):
The discussion label, which I think would fit here, is no longer a thing?
@Krzmbrzl commented on GitHub (Jun 5, 2021):
I think ditching this feature is fine. Especially if this prevents us from having to ask for special permissions
@sheepa commented on GitHub (Feb 7, 2023):
I still run 1.3 for this specific feature.
@Krzmbrzl commented on GitHub (Feb 7, 2023):
It can't be helped though. The new API doesn't support it and the old had serious input lag issues (system-wide), which is not acceptable 🤷
@davidebeatrici commented on GitHub (Feb 7, 2023):
Ideally the operating system itself should provide a way to configure a global filter, perhaps with granular control based on the application(s).