Microsoft Edge redirection mistakenly considered as HTTP protocol

[PHCCorso]

What's the issue?

Similar to: #26061

I get a validation error when I'm trying to redirect the user to Microsoft Edge, like in the example below:

<a href="microsoft-edge:https://www.google.com">Link</a>

[alanorozco]

cc @ampproject/wg-caching

[Gregable]

@PHCCorso can you provide a link to official documentation / spec for this protocol? It would be helpful to add that to the comments in your PR as well.

[twifkak]

I'm not @PHCCorso but I was curious so I did some quick digging. LMK what I missed (probably a lot :).

Here's some Windows-specific documentation.

On iOS, it apparently doesn't work; the alternative is microsoft-edge-https://.

I see some reference that it works on Android, but the official recommendation seems to be to use intent URIs.

Some other docs I found along the way:

• https://gist.github.com/felquis/a08ee196747f71689dcb
• https://dynamics.mittermair.pro/2019/01/29/browser-url-schemes/

[Gregable]

I'd be happy with your first link. This doesn't look like it'll work most of the time, but it won't be a security risk either. I'll add the comment in the PR review as well.

[PHCCorso]

I'm not @PHCCorso but I was curious so I did some quick digging. LMK what I missed (probably a lot :).

Here's some Windows-specific documentation.

On iOS, it apparently doesn't work; the alternative is microsoft-edge-https://.

I see some reference that it works on Android, but the official recommendation seems to be to use intent URIs.

Some other docs I found along the way:

* https://gist.github.com/felquis/a08ee196747f71689dcb

* https://dynamics.mittermair.pro/2019/01/29/browser-url-schemes/

Thanks!