A few months ago both Firefox and Brave added this workaround. Being able to modify the default app for the "microsoft-edge:" handler is something that was available since 2017 and pretty much EdgeDeflector was the main user. Most people back then said that Microsoft would never patch this thing but here we are.
Having a <0.1% of users bypassing your custom handler isn't relevant at all. But having 5~6% of them is not.
If your competitor (Microsoft) plays dirty and you play even dirtier (Brave, Firefox) at their own field, they will notice it, patch it and use it against you.
Since antitrust doesn't seem to work in the US... Maybe Microsoft will get another anti-trust fine from the EU and they'll forced to disable this handler at least inside the EU market.
What Microsoft is losing is mindshare with their customers.
It'll be a piece of cake, once their customers are angry enough, for a new tool to become popular that circumvents whatever "patch" Microsoft puts out.
Having a <0.1% of users bypassing your custom handler isn't relevant at all. But having 5~6% of them is not.
If your competitor (Microsoft) plays dirty and you play even dirtier (Brave, Firefox) at their own field, they will notice it, patch it and use it against you.
Since antitrust doesn't seem to work in the US... Maybe Microsoft will get another anti-trust fine from the EU and they'll forced to disable this handler at least inside the EU market.