We will support the newly added flag "allow-top-navigation-to-custom-protocols" which is specifically for navigation to custom protocols. I believe WebKit had implemented “allow-custom-protocol-navigation” and later renamed to "allow-top-navigation-to-custom-protocols" after the spec had been merged.
On Thu, 31 Mar 2022 at 20:15, Frederik Braun <[email protected]> wrote: > > > Paul Zühlcke <[email protected]> schrieb am Do. 31. März 2022 um 18:13: > >> Summary: >> Restrict opening external protocols from sandboxed iframes. In order to >> open external protocols sandboxed BrowsingContexts need to have any of the >> following sandbox flags: >> >> - >> >> allow-top-navigation-to-custom-protocols >> - >> >> allow-popups >> - >> >> allow-top-navigation >> - >> >> allow-top-navigation-with-user-activation >> >> Does this imply we do not support the “allow-custom-protocol-navigation” > flag that Chrome and Safari introduced? > > > > >> - >> >> >> -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAPdF9uMkDCxTU-ASUs5v_maadHJ9f6TWA-hVL_HTNaDBbLnT%3DA%40mail.gmail.com.
