It's quite interesting that if it's such a big security vulnerability Microsoft hasn't patched it in all these years, but when suddenly a browser maker wants to act in the users' best interests it's a "critical security vulnerability" that must be patched immediately.
Yes, malware could theoretically abuse the same loophole. But they simply cannot lie to our faces and say this is being blocked only to prevent malware when they've intentionally made it harder for users themselves to change the setting as well.
> It is quite normal that things break on the Windows Insider Preview builds from time to time right?
I run the Dev channel [1] (most frequent releases). And I don't think I've ever had anything actually break.Mostly it just makes my computer unusable every time they push an update, because it uses 100% disk capacity trying to background install while system is live. The background updates usually take 4-6 hours.
I also run Edge Dev and I HAVE had features break entirely on Edge, twice. Usually fixed within 1-5 days.
[1]: DON'T DO THIS! You cannot downgrade to Beta/RC from Dev, and it's the only channel that's like this!
Read the fine print. I receive updates sometimes multiple times a week and it's terrible.
I'm pro Free Software, and therefore anti-Microsoft, but isn't it possible that, because of the changes to URL requests, they just haven't implemented support for having a difference standard browser? And that it may come in the upcoming weeks?
This would be an all-time low for Microsoft. It would give them a lot of hate. I find that hard to believe to be honest.