>Interesting this is considered [Microsoft] Discord's fault and not Microsoft Windows.
Probably because Discord implements the button, no? They configure what happens when you press "X", so their configuration is in violation, not the platform.
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".
Discord's X button is implemented inside the webview and simply hides the window (to be revealed later by clicking the tray icon). It does not send WM_CLOSE or WM_DESTROY.
Alt+F4 is what actually closes the window, and in Discord's case, the entire rest of the app too.
>Over the past few years it has also become common for applications, including Microsoft Teams, to interpret "all windows closed" as "minimise to Systray".
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.
But Windows misrepresents that the application is not running, when it is running in the background with access to the mic. Is this not a poor default? The justification here is that Discord behaves differently from "the vast majority of applications". First, I'm not sure if that's true. Second, another justification brought up is that Discord doesn't show the user that their mic is still hot, Windows seems just as culpable for not "protecting by default".
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.
The issue highlighted in the article is no other VoiP/chat program will continue to record audio in the background. Which you can absolutely do, just don't make it the default behaviour. Valid point in my view.
Probably because Discord implements the button, no? They configure what happens when you press "X", so their configuration is in violation, not the platform.