Re:You can no longer bypass microsoft-edge:// links using a...
by pseudalopex on Thursday November 11, 2021 @03:10PM
(#29192532)
The article explained the details. Microsoft apps put microsoft-edge:// in front of links to make them open in Edge since Windows 10. People worked around it by having another app handle the microsoft-edge protocol. Now Microsoft broke that.
Re:You can no longer bypass microsoft-edge:// links using a...
by oneplane on Thursday November 11, 2021 @04:31PM
(#29193456)
That's what it explained yes, but that doesn't cover the protocol handler on the shell side at all. Either it's a protocol with a protocol handler or it isn't.
Re:You can no longer bypass microsoft-edge:// links using a...
by pseudalopex on Thursday November 11, 2021 @05:24PM
(#29194039)
Your meaning is entirely unclear. It was a protocol users could configure like the rest. Now they can't.
Re:You can no longer bypass microsoft-edge:// links using a...
by oneplane on Thursday November 11, 2021 @06:23PM
(#29194538)
Yes, that is the functional description, and I was writing about the technical implementation. User overrides work on protocols, but if it's not a user override anymore it makes sense that it wouldn't apply the settings since there is nothing to apply to.
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.
Re:You can no longer bypass microsoft-edge:// links using a...
by pseudalopex on Thursday November 25, 2021 @05:26AM
(#29340027)
The details you dismissed established it wasn't accidentally hard coded. And Microsoft admitted it was intentional.[1]
[1] https://www.zdnet.com/article/microsoft-doubles-down-on-its-...
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.