One workaround I have used before is to create separate copies (NOT symlinks) of the chromium.bin executable, and make launchers use those instead of the system chromium.bin. But this is annoying to deal with on upgrades and also doesn't scale particularly well to lots of web app launchers.
One workaround I have used before is to create separate copies (NOT symlinks) of the chromium.bin executable, and make launchers use those instead of the system chromium.bin. But this is annoying to deal with on upgrades and also doesn't scale particularly well to lots of web app launchers.