We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Making a call in Teams binds the multimedia keys (play/pause/etc) to Teams so that they no longer work with media applications (e.g. Spotify).
To Reproduce Steps to reproduce the behavior:
Expected behavior
Since Teams isn't a media application, it should have no impact on the multimedia keys
Screenshots
N/A
Desktop (please complete the following information):
Additional context
Electron seems to bind to the multimedia keys by default.
It seems that this can be disabled relatively easily:
app.commandLine.appendSwitch('disable-features', 'HardwareMediaKeyHandling');
(electron/electron#18253 (comment))
The text was updated successfully, but these errors were encountered:
feat: Disable hardware media key handling
bced0c8
Fixes IsmaelMartinez#716
@bmaupin this went unnoticed. there were some merges happened. Could you pull again and also update the version in package.json?
Sorry, something went wrong.
6f44ffd
... and bump version to 1.0.58 Fixes IsmaelMartinez#716
Successfully merging a pull request may close this issue.
Describe the bug
Making a call in Teams binds the multimedia keys (play/pause/etc) to Teams so that they no longer work with media applications (e.g. Spotify).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Since Teams isn't a media application, it should have no impact on the multimedia keys
Screenshots
N/A
Desktop (please complete the following information):
Additional context
Electron seems to bind to the multimedia keys by default.
It seems that this can be disabled relatively easily:
(electron/electron#18253 (comment))
The text was updated successfully, but these errors were encountered: