As an IT person - I openly admit "Broken" IS a trigger word. I hate thinking that something I've built doesn't work correctly. It triggers me to Do My Job and fix the problem. And then, I Thank the person who pointed it out. Coding is a big messy world, things will break - people who report the errors are Helping you out! There's ZERO excuse for this bug being left uncorrected for so long. There are millions of people whose workflows involve having a window open in the background. It's not even a topic worth debating. Someone at MS is being lazy and/or living in denial about their own work/skills/abilities. Just get over it and fix it. Do your job.
Thank you for your response. I think what surprised me at r/microsoft was how quickly respondents attacked me personally right out of the gate. Again, I don't know how many of these personal attacks came from Microsoft professionals, but they did help to confirm my concern that something is amiss.
I've been using Windows since version 3.1 was released in 1992, and while I've seen a lot of issues, never have I encountered one so productivity-impeding as this.