4 ms·
Why bother? I already know no one will talk about this in 3 weeks because its resolved and wont ever affect anyone running the release versions anyway.
by noxer 5y ago
Why bother? I already know no one will talk about this in 3 weeks because its resolved and wont ever affect anyone running the release versions anyway.
- xg15 5y agoWill it? So far it seems they are pretty persistent in blocking all workarounds. I don't think the users will bother so much, but the other browser vendors might take issue.
- noxer 5y ago>they are pretty persistent in blocking all workarounds Weird interpretation of reality. Nothing is or has been blocked on the windows people actually use. Its only broken on a single dev build.
- xg15 5y agoI mean, we'll see. If you're right and this really was just a technical mistake, more power to you. But to me, the change looks pretty deliberate. And if it was, I see no reason why Microsoft would want to fix it - at least without significant external pressure.
- xg15 5y agoAddendum: It's officially mentioned in the release notes [1]: > We fixed an issue where OS functionality could be improperly redirected when microsoft-edge: links are invoked. [1] https://blogs.windows.com/windows-insider/2021/11/12/releasing-windows-11-build-22000-346-to-beta-and-release-preview-channels/ https://blogs.windows.com/windows-insider/2021/11/12/releasi...
- noxer 5y agoYou can use https://github.com/rcmaehl/MSEdgeRedirect https://github.com/rcmaehl/MSEdgeRedirect Also this https://github.com/da2x/EdgeDeflector/issues/142#issuecomment-968687701 https://github.com/da2x/EdgeDeflector/issues/142#issuecommen... setting might me important for some people.