You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using Zulip and are having a problem for some of our custom launcher we'd link to linkify.
The links are :// unfortunatly this will always be opened in the browser as the custom protocol is not part of the list. ["http:", "https:", "mailto:"]
Would there be an option to ad custom protocol launcher to the settings which will look like:
"protocolLaunchers": {
"": "mylauncher",
}
This is an option which might gives the opertunity that users can create clickable links which e.g. open files in applications while keeping the secruity menitoned in:
// For security, indirect links to non-whitelisted protocols
// through a real web browser via a local HTML file.
As the protocolLaunchers can be configured manually.
What do you think about this, happy to help/cotnribute this with a PR if it's cool :)
The text was updated successfully, but these errors were encountered:
Hey,
we are using Zulip and are having a problem for some of our custom launcher we'd link to linkify.
The links are :// unfortunatly this will always be opened in the browser as the custom protocol is not part of the list. ["http:", "https:", "mailto:"]
Would there be an option to ad custom protocol launcher to the settings which will look like:
"protocolLaunchers": {
"": "mylauncher",
}
In https://github.com/zulip/zulip-desktop/blob/main/app/common/link-util.ts
The pseudo-code my look like:
This is an option which might gives the opertunity that users can create clickable links which e.g. open files in applications while keeping the secruity menitoned in:
// For security, indirect links to non-whitelisted protocols
// through a real web browser via a local HTML file.
As the protocolLaunchers can be configured manually.
What do you think about this, happy to help/cotnribute this with a PR if it's cool :)
The text was updated successfully, but these errors were encountered: