New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 710 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2015

Sign in to add a comment

Chromedriver doesn't attach to chrome instance launched by manual

Reported by, Feb 19 2014

Issue description

See for common issues.

Issue Description:
Chromedriver doesn't attach to chrome instance launched by manual.
Is it by designed? Or there is anyway for me to achive it?  
It seems chromedriver can only controls the chrome instance which created by itself.

Steps to reproduce:
1. Launch chrome.exe manually;
2. Launch chromedriver.

Not sure if this is by design, anyway I need to launch chrome by manul firstly for a specific requirement. Weather there is a solution to solve it? Or I need to change source code of chromedriver? 
Status: Unconfirmed
You can use the debuggerAddress in ChromeOptions to achieve this, but a few commands won't work (e.g. window resizing, since this depends on the automation extension, which chromedriver loads when it launches chrome).

More documentation is available here:
Status: WontFix
Start chrome browser manually using --remote-debugging-port=xxxx.
Through chromedriver launch chrome with debuggerAddress option.

Launch Chrome from command prompt:
chrome.exe --remote-debugging-port=8181

Sample Code:
		ChromeOptions options = new ChromeOptions();
		options.setExperimentalOption("debuggerAddress", "");
		WebDriver driver = new ChromeDriver(options);
		driver.manage().timeouts().implicitlyWait(1, TimeUnit.MINUTES);

Closing issue
If any facing similar issue please raise new issue

Sign in to add a comment