Bug 118615 - Possibility to launch multible browsers with separate sessions
Summary: Possibility to launch multible browsers with separate sessions
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 321845 431210 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-30 06:46 EST by Pasi Lehtimäki CLA
Modified: 2017-06-26 11:46 EDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pasi Lehtimäki CLA 2005-11-30 06:46:35 EST
I need to be able to create a multipage editor with a swt browser on each page. Each of these browsers need to have different session. This is needed when building a tool to test a web application. Currently each of the browser components share the very same session and that causes problems.
Comment 1 Veronika Irvine CLA 2005-12-08 12:55:08 EST
On Windows, it does not appear that there is any way to have different session data for multiple embedded IE controls running in the same process.

We have been looking for a solution to this problem for some time now and so far have not found an answer.

In 3.2, Grant added the ability to clear session data (Browser.clearSessions()) which will clear the session data - but this again is the data shared by all the embedded browser instances.
Comment 2 Saminda Wijeratne CLA 2009-11-17 12:57:56 EST
any update on this?
Comment 3 Grant Gayed CLA 2009-11-17 14:08:37 EST
No update, except that there isn't currently support for this in the native browsers used by the SWT Browser.  If this becomes natively supported then it would be a great functionality to expose.
Comment 4 Grant Gayed CLA 2010-08-17 16:28:01 EDT
*** Bug 321845 has been marked as a duplicate of this bug. ***
Comment 5 Grant Gayed CLA 2014-03-31 14:58:00 EDT
*** Bug 431210 has been marked as a duplicate of this bug. ***