That is something entirely different. When I said active user input, it was a concrete reaction to a specific user action, like moving the mouse at the menu area. There is no such user action, which would be triggering a sound recording. This is about running applications in the background. According to the article, that would taint the full screen mode constantly and not transiently as the other actions. It is fully sufficently, if that happens on the primary screen.
I understood that. You are not understanding the problem or pretending to. Imagine a powerpoint presentation during a video conference. I don't want the presentation overlaid by a yellow dot. There was no such thing like that so far. At minimum, there need to be controls to prevent that.
And I'm telling you yes there is. You could still get an alert from Steam logging in on your full-screen app. You could get a Windows Visual C Runtime Error that pops up on top of it. You could get a macOS notification or a kernel panic report and it would pop up right on top of your full screen application. Apps cannot override the I/O system of the OS.
I never claimed they can. But so far you can run an app in full screen mode and unless a special event happens, you won't get something on top of it. The audio indicator is completely different, because as long there is audio recording in your system, you don't seem to be able to get rid of it. At no time. If nothing exceptional happens on your system, the OS should allow full-screen apps to run. So far, all OSes did so.
