Note that this issue is specifically about microsoft-edge:// links (used in some internal Windows features). Not http/https.
I do wish they used a more generic/portable solution, but this is for Windows-specific features, so it would require them to think through an open, stable & forever-supported API...
I do wish they used a more generic/portable solution, but this is for Windows-specific features, so it would require them to think through an open, stable & forever-supported API...