Bug 50376 - WebKit shares browser session with Safari
Summary: WebKit shares browser session with Safari
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 00:27 PST by Martin Häcker
Modified: 2013-06-06 04:27 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Häcker 2010-12-02 00:27:25 PST
Hi there,

when using Safari and WebKit in parallel it shares a session. I.e. when I quit one browser and then open the other and choose "restore all tabs" I get the tabs from the other browser.

Which is very annoying as I use one (Safari) for browsing and the other (WebKit) for developing and validation of pages.

But I can't disable this behaviour.

So please make the sessions distinct - perhpas add an option that you can share or import the other browsers session as a debugging feature.s
Comment 1 Alexey Proskuryakov 2010-12-02 12:02:07 PST
WebKit is not a browser - it's only a framework Safari uses. So, running a WebKit nightly is no different from launching multiple instances of Safari in this respect.

"Restore All Tabs" is a Safari feature, and thus offtopic for bugs.webkit.org.

Note that Firefox nightlies simply won't launch if released Firefox is already running. That's a way to resolve this problem, but I think that letting both versions run side by side is superior, even if that causes issues due to sharing saved state.
Comment 2 Martin Häcker 2010-12-04 08:08:13 PST
Well, why not give them separate identities? It can't be that hard, since it should all depend on the application identifier - and the name of the application is already different.

That would be even more consequent, and solve the confusion that arises from having two different looking (golden or blue) applications with different names (WebKit and Safari) that never the less have remarkable hard to explain influence on each other?

Regards,
Martin
Comment 3 Alexey Proskuryakov 2010-12-04 11:35:13 PST
The reason for WebKit nightly existence is early testing - if nightlies had separate preferences, history, caches etc, then it would be much harder to tell whether a problem is a true regression, or just caused by a different saved state.
Comment 4 Martin Häcker 2013-06-06 04:27:05 PDT
Is there any known workaround for this bug report?

To repeat the use case: I would like to use Webkit Nightlies for development and to detect bugs in it. To set up a development environment I would like it _not_ to share a session with Safari, so it can have it's own bookmarks and does not share open windows with Safari. Also I want to regularly get rid of caches in Webkit Nightlies while retaining them in Safari.

Till now my workaround has been to just use Chromium, as that was just WebKit with a different UI but with no shared session.

But I'd like to get off of Blink now and use Webkit Nightlies.

So is there any recommended workaround to have the two applications not sharing state?