O Ven, 20-01-2017 ás 10:24 +0100, Carlos Garcia Campos escribiu: > In the past WebKit used the enablePrivateBrowsing setting that was > checked everywhere when needed. Now, pages have a session ID > associated. There's a default session ID, and any other ID is > considered ephemeral. So, to enable private browsing we just need to > associate the page to any session ID different than the default one. > The main different is that now in WebKit2 at least, the association > happens on WebPageProxy construction, so it's not possible to > enable/disable private browsing in a WebKitWebView, you must create a > private or non-private web view. With the WebKit2 C API, this is > achieved by creating a non persistent WebsiteDataStore and pass it to > the WebPageProxy as PageConfiguration.
I think this makes sense because there are a lot of things that could be leaked to the incognito session if you are not careful enough, like caches, cookies, databases... BR _______________________________________________ webkit-gtk mailing list webkit-gtk@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-gtk
