A bit like:
- "openInBrowser(url)" (the mistake)
- "openInEdge(url)" (the malice)
- "openInDefaultBrowser(url)" (the one configured by the end-user).
I have no idea what they are doing under the hood, but I'm pretty sure some of it can be easily identified for being a mistake, malice or something else. But because I don't know, and apparently neither do most people here, speculation on the effect being the main intent or a side-effect alone is iffy at best. The functional outcome remains the same of course, and I'd rather start out with calling it a bug than anything else. If Microsoft then comes out calling it "works as intended" then yes, that's just nasty.
Just because it "looks" the same doesn't mean it is the same. There is a vague reference about a few KiB of added compiled code and the fact that it's an insider build, but other than that just an exploration of previously valid avenues that no longer apply, and the bundled outrage of assumptions based on a whole lot of nothing.
I don't know what the actual implementation is, the article on the website doesn't seem to know, and neither do you. So all we can do is speculate, and it appears some people choose unproductive outrage over technical exploration.
[1] https://www.zdnet.com/article/microsoft-doubles-down-on-its-...
This was already done.
The new ticket would have said something like: "Stop users from being able to override the special links that only work in Edge. Make very sure that users have no way of working around this behavior even if they really want to."