For example, on my Android phone, whenever the mic/camera is in use, even if the app is in the background, the OS displays a green dot in the corner of the screen and when I poke it, it tells me what is using the mic/camera. This is a good default.
I don't think Windows is culpable instead of Discord, but I do think that more protection should be built into Windows, and based on this decision, Windows could get dinged for this as much as Discord.
In my experience; quite a few programs will minimize to system tray when pressing x.
Just tested in a call with Skype. Closing the windows still has the program running, recording, and the call is still active.
Ditto Camfrog.
Ditto Paltalk.
That's because most actual programs have a 'minimize to tray on closing' option enabled by default on install.
It's been like this since 1998 or so. I've been undoing that option for at least 20 years, because when I click X I expect it to GTFO.
Pressing X or Alt-F4 sends WM_CLOSE to the window. By default this is converted to WM_DESTROY and closes the window. By default, an application with no more windows open will exit.
It's quite normal for applications to intercept WM_CLOSE, for example with a modal dialog of "Do you want to save your files?".
Over the past few years it has also become common for applications, including Microsoft Teams, to interpret "all windows closed" as "minimise to Systray". Microsoft also responded to increasing use of the systray by auto-hiding most apps in it.
The issue is not "minimise to systray" per se, it's "sending user voice when the user thought they'd closed all the windows".
(bonus stackoverflow: you can separate the behavior https://stackoverflow.com/questions/9788662/how-do-i-repurpo... )
Alt+F4 is what actually closes the window, and in Discord's case, the entire rest of the app too.
More like the past few decades. Seriously, this has been a thing (usually configurable in app settings, and common in many long-running applications like messengers and music players) for as long as I can remember.
Probably because Discord implements the button, no? They configure what happens when you press "X", so their configuration is in violation, not the platform.