To me it would be even more useful to be able to attach webdriver to an existing
window (e.g. in a popup opened from another page). I'll still had my vote on this issue.

I agree - ability to attach to existing session or better yet, switching between sessions
at will would be of great use.

This feature will help us a lot on unit testing and debugging on the code for a particular
page.

Ya I definitely need this too.

agree can someone get this added :)

I'll add my 2cents and say I really could use this as well.  I have a browser page that
acts as a menu to kick of various reports and other functions. I'd like my test suite
to start the browser and go to the menu page. From there each test case/class tests
a report. But I'd like to also run the tests ad hoc, running each test from the menu
page without starting/stopping the browser each time.

I also really need this capability. I am trying to port an existing test suite from
Watir. I have tests that look for the presense of popups as well as test their content.
Being able to attach to another window is essential and will allow me to upgrade to
the watir webdriver api.

leonashleydavis: That sounds like a different use case. Although it's not exposed in
watir-webdriver (yet), you can access the underlying Driver instance and use its API
to switch between windows, e.g.:

>> b = Watir::Browser.new :firefox
=> #<Watir::Browser:0xf10318 url="about:blank" title="">
>> b.driver.window_handle
=> "{f5da02dc-6c66-481e-85b4-6aea9973b44c}"
>> b.driver.window_handles
=> ["{f5da02dc-6c66-481e-85b4-6aea9973b44c}", "{2d99ce5c-b4c9-4ec0-8edc-7ec59ba10cd0}"]
>> b.driver.switch_to.window("{2d99ce5c-b4c9-4ec0-8edc-7ec59ba10cd0}")
=> "d74e5e46-7c4c-42db-979b-d5f80ed5c6b3"
>> b.driver.window_handle
=> "{2d99ce5c-b4c9-4ec0-8edc-7ec59ba10cd0}"
>> 

If you have suggestions for what a Watir API for this should look like, please comment
on this issue: http://github.com/jarib/watir-webdriver/issues/issue/34

Can I also attach to a browser that was not started by Watir?

This is possible with standard Watir. 

I agree with this.  I could really use this for our Company.  This would allow us to
automate the starting of the browser and get around some of the screens that are not
currently supported by the webdriver.  Then we could attach the webdriver to the browser
and run from selenium from that point.

Simon, lets chat about this tomorrow. I think we can get a hold of it by storing a PID
when we launch and the sessionId.

Simon, do you think this is some thing that could be included in the upcoming Beta 2
release. Seems like with the new rewritten IE driver if you expose few methods this
should be possible.  I could really use this for our company as well.

The IE driver was rewritten to make this scenario easier, but without an exposed API
in Selenium/WebDriver, we don't have any way to make it happen. You probably won't
see this API exposed for beta 2.

agree

You may be interested in what I have implemented as PersistentWebdriver class that allows
to attach to a running session:

https://gist.github.com/852560

Note: it is tested only with Firefox (on ubuntu)

I implemented this in se1, feel free to take a look.

github.com/antlong/selenium

Was this feature included in beta 3? if Not when is it likely to be part of the selenium
API? this is a very useful feature

I also need this feature as my browser is embedded in another application.

Would be a very handy feature. Our is a web start application. This feature would help
us a lot.

This feature is critical for test cases where part of the test requires manual intervention,
then we need the automated test driver to take over for a while.

Seconding #19 ... when will we see this feature in the beta or in release?

Thank you Anthony for implementing it!

I am also very interested in this feature.

I think it would be great if we could get handle to the pened browser session. Since
my project require the check the flow in various stages for thar i have to swith between
the applications.

This feature will be very useful as an recovery process for all automation scripts we
have.

This would be awesome! There are a few parts of our native application that open a browser.
From there it would be really nice to let Selenium take over and continue with the
automation.

This would be a great feature. This feature will help QA to write test scripts in much
faster way. It allows users to work on any web page by simply attaching that browser
page to the respective webdriver by passing brower "Title" rather starting from first
page. I am not sure whether should I attach sample code or not. I used this technique
with WATIN as mentioned below:

// Get the focused browser window title
String WinTitle = NativeWin32.GetText(NativeWin32.GetForegroundWindow()).Substring(0,
NativeWin32.GetText(NativeWin32.GetForegroundWindow()).LastIndexOf('-')).Trim();

// Attach this page to IE browser
driver = IE.AttachTo<IE>(Find.ByTitle(WinTitle));

This would be an awesome feature to add, and really help with test debugging so a user
can isolate and run a single step instead of having to run the test from the beginning.

Really need this feature soon!! It will be very useful..

Anthony, thank you for implementing this; I'm a Java newbie, could you or another poster
give an example of instantiating this PersistentWebdriver class?  I'm still using the
old WebDriver with Firefox that had this feature, but will upgrade once I can get the
class to work for me.  Thanks much!

Also, why was this feature removed from WebDriver when it worked in earlier versions?

Issue 2507 has been merged into this issue.

This feature would save a lot of time and nerves of automated testers. Alternatively
could anyone post a workaround for C#?

this would be a great feature for me too

Issue 3121 has been merged into this issue.

Issue 3229 has been merged into this issue.

Issue 3457 has been merged into this issue.

Issue 2163 has been merged into this issue.

Issue 3538 has been merged into this issue.

Issue 3927 has been merged into this issue.

Issue 6417 has been merged into this issue.

I'm going to make a call on this one: it's a browser specific feature, and not something
that we can implement in a general way. With IE, it's possible to iterate over the
open windows in the OS and find the right IE process to attach to.

Firefox and Chrome, OTOH, need to be started in a specific mode and configuration,
which means that just attaching to a running instance isn't technically possible.

Closing as "not feasible" here as this is a browser specific feature.

Issue 7004 has been merged into this issue.