Forum Discussion
Not allowed to launch <external_protocol> because a user gesture is required
Hi,
I'm trying launching an external 3rd party app on Win10 via Edge using an external protocol, something like jacopop: but after being redirected successfully to the app once, if I try again, the app never launches and the Edge console shows the error above ("Not allowed to launch jacopop: because a user gesture is required").
I understand this is an anti-flooding feature in Chromium (https://techcommunity.microsoft.com/t5/discussions/not-allowed-to-launch-jnlps-host-port-cws-zbsl-zbsl-jnlp-because/m-p/3000820#M50983) and (https://bugs.chromium.org/p/chromium/issues/detail?id=1273626) but I don't get the same behaviour in Google Chrome or any other browser, just in MSFT Edge. The only way to get it to work in Edge is to have to click somewhere on the webpage and refresh the page to get redirected, but it would be much better if users could be redirected multiple times within the same Edge session.
Is Edge going to follow Chrome and disable this feature?
Thanks!
1 Reply
- Eric_Lawrence
Microsoft
JacopoG Chrome and Edge have the same code here, except that Edge has an additional policy DoNotSilentlyBlockProtocolsFromOrigins that is not present in Chrome.
The reason you see different behavior in one browser vs. the other is almost certainly related to a bug in Chromium and the extensions you have installed. Specifically, if you have a browser extension installed, every API call it makes resets the flag that bypasses the gesture requirement. This is a bug that Chromium will eventually fix.
You can learn more in https://textslashplain.com/2019/08/29/web-to-app-communication-app-protocols/
Currently, flood prevention in Chromium does not work very well, suffering both false positives and false negatives.
