Bug 83367

Created attachment 136103 [details] first option Patch to better get idea about first solution. Adding a setCookiePath property to experimental. Thought?

(In reply to comment #1) > Created an attachment (id=136103) [details] > first option > > Patch to better get idea about first solution. Adding a setCookiePath property to experimental. Thought? I don't think this should go into experimental, because I think we can already say that it is highly unlikely that this "experiment" will succeed, i.e. that we will take this property as-is into the public WebView API. At best I think this qualifies as private C++ API. Why do you want to change the cookie storage path at run-time? Currently this is a part of the process creation parameters, which seems like the right place. Could you get it in there somehow for your use-case?

The issue I have is that a WebView cannot decide where its cookies will be stored (and loaded from). We need such functionality to login into two different google accounts (for instance) and avoiding sharing the cookies between the two views, and also to be able to store the cookies in a per-account directory so that we don't have to re-login each time. We are currently achieving our goal by starting a separate process with a different HOME variable set, then we open a WebView from within this process and in this way we can hack through the issue. But it's far from ideal.

=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.