https://bugs.kde.org/show_bug.cgi?id=418434
--- Comment #4 from Andreas Kilgus <k...@fuenfsieben.de> --- (In reply to Juraj from comment #3) > > Maybe "one process for each activity" is required to support activities. > This would mess up current settings and so on if you use same profile for > all oft hem. Well, just for comparison: 23 konqueror processes running on my machine in 4 activities just now - no mess of settings. But that's the wrong discussion anyway (at least with me as counterpart). I consider it a bug that the nowadays main/default browser of KDE applications does not support activities. The way how this lacking can be changed is beyond my scope/expertise. > A bit crazy workaround I can think of is using different profiles for each > activity, in such case there would be new process created. > > > falkon -r -p <my-cute-little-profile> That's the way activityfox works (well, more or less) for chromium and firefox. One profile/activity. But s. https://bugs.kde.org/show_bug.cgi?id=396291#c2 - this has several flaws. And does not work for Falkon: Start activity, execute "falkon -r -p test" (BTW: I don't like the idea of having to repeat all my configuration work for every new profile from scratch), stop activity, start activity - the restored Falkon window belongs to the default profile, not to "test". -- You are receiving this mail because: You are watching all bug changes.
