As in chromium Ubuntu's launcher, it would be useful when testing/debugging to add --temp-profile switch to chromium-launcher to launch chromium in a separate instance with an empty profile. I attach a patch with this feature (largely inspired from ubuntu's launcher, credits to original author).
Created attachment 258798 [details, diff] Patch adding --temp-profile switch
Created attachment 258799 [details] Ubuntu's launcher for reference
I think it's a nice thing to have, but doing this at the distro level risks many inconsistencies and maintenance problems. Could you instead open an upstream feature request (new.crbug.com), and post the link here?
Do you mean this switch should be implemented upstream in a launcher script (I don't know if it currently exists) or in native code? If in native code, doesn't it conflict with native --user-data-dir switch? Nevertheless, I will open an upstream feature request but I would like to know your opinion, Paweł, if any...
(In reply to comment #4) > Do you mean this switch should be implemented upstream in a launcher script (I > don't know if it currently exists) or in native code? > If in native code, doesn't it conflict with native --user-data-dir switch? I'm not sure which solution would be better. Also, the conflict should be easily solvable by forbidding passing both flags, or making one of them override the other. Note that the upstream may decide to reject the idea. However, there is at least one existing use for it: the test framework makes each browser under test run with a fresh profile. Currently --user-data-dir is used "from the outside", but by converting to --temp-profile we shouldn't increase the overall complexity.