I'm sorry to say we were forced to move from Chromium to Google Chrome (unconfined deb package). I am not at all happy with that, as our software is now less secure than it was before (with the unconfined Chromium). But I never managed to get the snap running for my users, snaps are just not designed to work in networks. Missing URL handlers was the least of our problems. Not being able to access network shares and snaps caching into the users's homes was what made it unusable. Very sad that a decision that supposedly was meant to make Chromium more secure has caused right the opposite for us.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
