<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [SOUP] Fix handling of accept language property"
href="https://bugs.webkit.org/show_bug.cgi?id=166969#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [SOUP] Fix handling of accept language property"
href="https://bugs.webkit.org/show_bug.cgi?id=166969">bug 166969</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=166969#c5">comment #5</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=166969#c3">comment #3</a>)
> > It is. Open MiniBrowser and enable private browsing in the settings, for
> > example. The other case is testing,
> > NetworkStorageSession::switchToNewTestingSession() creates a new session
> > that is private from the cookie storage point of view, but non ephemeral
> > from the session point of view, so it replaces the default session.
>
> If we support private browsing session now, should we be using that in
> Epiphany...?</span >
We have always supported private browsing, another thing is that it has always been broken :-P I don't think it's ready for ephy yet, at least custom uri schemes doesn't work in private browsing mode, but it might be the only thing left to do. Then, yes, I think it's safer to enable private browsing in ephy, it might cover cases for which we are still writing outside the ephy profile dir.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>