Forum Discussion

AndrewSAIF's avatar
AndrewSAIF
Iron Contributor
Mar 02, 2020
Solved

ExternalProtocolDialogShowAlwaysOpenCheckbox policy no longer works in Edge Dev and Canary

Hi there,

 

We have the ExternalProtocolDialogShowAlwaysOpenCheckbox policy enabled so that folks can have the browser remember their preference for frequently-used protocol handler links. It looks like this policy still works in Edge Beta 81.0.416.20, but stopped working in Edge Dev 82.0.432.3 and later. The checkbox is simply not shown in the later versions. I tested using skype:// and another application we use in-house. The policy is visible in edge://policy, but it is ignored for whatever reason.

 

Thanks!

Andrew

 

 

  • todd_sahl's avatar
    todd_sahl
    Mar 30, 2020

    AndrewSAIF 

     

    Hi Andrew,

    This policy to show the checkbox was recently restricted to only work from secure (i.e. https) pages.  I suspect that you are expecting to see the checkbox from a non-secure page and that it is not showing up.  

     

    Can you confirm?

     

    This change was made as part of a broader set of changes to the opt-out checkbox, including:

    • The checkbox now applies per-origin.  So if you select the checkbox because you tried to launch skype: from sharepoint.com, that combination will skip the prompt in the future, but other origins will still see the prompt when launching skype: until opted out.
    • The checkbox will be turned on by default for all users in an upcoming release, so that the group policy is no longer needed.  It will continue to be possible to ensure the checkbox is never shown by explicitly disabling the policy though.

    Todd

21 Replies

  • AndrewSAIF   Could be good news on the horizon.

    Just looked on the beta v84 version of Edge, and the documentation says:

     

    "As of Microsoft Edge 84, if you don't configure this policy, when an external protocol confirmation prompt is shown, the user can select "Always allow" to skip all future confirmation prompts for the protocol on this site"

     

    Hopefully v84 of Edge will honour the setting, same as Chrome

     

    https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#externalprotocoldialogshowalwaysopencheckbox 

     

    • AndrewSAIF's avatar
      AndrewSAIF
      Iron Contributor

      RichardStantonPropsoft 

       

      Hm, maybe I'm missing something, but the example I gave (skype://) still shows me a checkbox with this policy enabled on Edge Stable 81 and still does not show me a checkbox on Edge Canary 85. 

      • AndrewSAIF's avatar
        AndrewSAIF
        Iron Contributor

        Deleted todd_sahl 

        It looks like a solution to this problem is to add the URLAllowlist policy, then add your handler to that:

        https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#urlallowlist

         

        Use this format:

        handlername://*

         

        Hope this helps someone. This definitely wasn't clear from the description of the policy. Maybe this isn't even intended behavior, but I'm sure glad it works. 

         

        Andrew

         

  • AndrewSAIF's avatar
    AndrewSAIF
    Iron Contributor

    Not the solution I prefer, but it looks like as a workaround I can just throw the page on my IE Mode list. No popups at all. 

     

    Andrew

    • Anonymous's avatar
      Anonymous

      AndrewSAIF Thanks for reaching out and letting us know. We're sorry to hear that it isn't working! We just pushed 83.0.470.0 to Canary; are you still seeing this behavior there? If so, let us know and we'll loop in the GPO team. And in the meantime, can you please submit detailed feedback and diagnostic data through the browser, if you haven't yet?

       

      Fawkes (they/them)
      Project & Community Manager - Microsoft Edge

      • Mike_Nunan's avatar
        Mike_Nunan
        Copper Contributor

        Deleted 

         

        Hi,

         

        I just encountered this issue too and would like to add my voice to those here requesting a fix.  For our use case we are interested in the behaviour when a custom URL is entered directly into the address bar, as well the case where the link is placed in a page with an HTTP URL rather than HTTPS.  As others have said, in all cases this impacts UX quite badly, it is a blocker for Edge adoption for us at this time.

         

        Kind regards,

         

        Mike

Resources