frontend: Duplicate browser cookies when profile is duplicated#13472
frontend: Duplicate browser cookies when profile is duplicated#13472WizardCM wants to merge 1 commit into
Conversation
Fix regression introduced by obsproject#11055
|
My first gut reaction is that the call to Placing it after |
|
Yeah, the more I've been thinking about this, the more I agree it needs to be part of Based on my understanding so far, there's one major flaw with the current implementation: I think the flow has to be
I'm unsure if keeping a separate |
|
One thing that just occurred to me (but haven't researched this) is that So just calling it when the code is actively duplicating a profile (and where it has that context information) is a good-enough solution if you're still comfortable with it as well. Maybe just add a task issue and note it with a ToDo here so we don't loose track of this cleanup/refactoring task maybe. |
Description
Regenerate Cookie ID and copy existing cookies into a new folder when duplicating a profile.
Without this change, cookies are reused across profiles, so logging out of one logs out of both. This causes very unpredictable behaviour.
Motivation and Context
Reproduction Steps:
config\obs-studio\plugin_config\obs-browser\obs_profile_cookiescontains 1 directory.config\obs-studio\plugin_config\obs-browser\obs_profile_cookiesdidn't gain a second directory.basic.inihave the same[Panels] CookieIdHow Has This Been Tested?
CopyCookies1CopyCookies2obs_profile_cookiessubdirectory was created that matches the value inCopyCookies2'sbasic.iniand that the[Twitch]section remains identical in both.Tested on Windows 10.
Types of changes
Checklist: