Forum Discussion
ExternalProtocolDialogShowAlwaysOpenCheckbox policy no longer works in Edge Dev and Canary
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
Deleted
Hi Fawkes,
I updated Canary to the latest version and got the same result. It is easy to duplicate this behavior on a machine that has Office installed if you set the policy, then type skype:// into the address bar and press enter.
I have the feedback feature disabled in my group policy, but if that is a better way to report issues I can set up a test machine to be excluded.
Thanks!
Andrew
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
- Hi Todd,
This restriction ruins intranet app experience. Will there be a change in this restriction?
Omer todd_sahl Deleted
Hi there. Is there any update on the status of this policy? The behavior appears to be the same still in v85.Thanks!
AndrewSAIF Our customers are in a similar position, their intranet has specific rules which mean they've twice tried to migrate from IE11 to Edge but had to revert (the most recent to Chrome).
I was hoping with the Chrome based version of Edge that it would honour ExternalProtocolDialogShowAlwaysOpenCheckbox in either Chrome or Edge's reg keys.
The annoyance to the customer of having to click the popup confirmation each time is a deal-breaker,
Hi Todd,
Thanks for the quick reply. Yes, I am expecting to see the checkbox from a non-https site.
The reason this policy was useful to me is because we have web apps on an http intranet site that contain protocol handler links to open a separate application. For various reasons, we cannot easily make these sites HTTPS.
For this use case, users are clicking several of these links in a short timeframe. The popup for confirmation becomes very obtrusive. I was excited to have this policy since the only other solution at the time was to manually edit the preferences file (or script it).
There was a backlash when this checkbox was removed from Chrome from enterprise users, and I thought this policy was a response to that backlash. I don't think my use case is uncommon and I suspect this will be a big deal for several organizations.
Do you have a timeline or version target for when the checkbox is available by default, and when this happens will the checkbox still only appear for HTTPS?
