Implement page load timeout API about chromedriver HOT 28 CLOSED

Issue 23 has been merged into this issue.

You are right. This is a huge problem, and it needs High priority. It is 
discussing here 
http://stackoverflow.com/questions/9876529/make-browser-stop-loading-page

hi, could you please provide any estimates on when this feature will be 
released?

This feature is slated for release in April-June. What is slowing (or hanging) 
your page load? You might could check the developer tools or the chrome net log 
to see what is taking so long.

I'm not sure this issue deserves high priority. It is not implemented in any 
other driver except for Firefox, right?

If you look at my report (Issue 23), you'll see that Chromedriver frequently 
becomes unresponsive/refuses to accept further instructions. From what I 
understand, this ticket won't address Chromedriver hangs, but will provide a 
built-in way to timeout (no need to create your own timeout mechanism with 
socket timeouts or threads).

Yes, I agree with [email protected]
This is the main reason why i'm wondering when this feature will be developed 
and released.

IE now has support for this too (well, it will in 2.22).

The wire call is defined here:
http://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/time
outs

for this issue it's 'page load'

But this wire call also can take 'implicit' or 'script' as the type, 
essentially aliases of the other end points. When 'page load' is taken care of 
can the aliases be too? (or should I log a new issue?)

I'm needing this ability as well.  I'm testing an enterprise application where 
loading times can often exceed 60 seconds, especially when we test with the 
system under load.  Currently, I can't use Chrome for these test scenarios due 
to not being able to change the page load timeout.

This would be rad to have now.

Any suggestions for emulating the behaviour of this functionality?

yes, try working directly with chrome. add an extension to the browaser:
https://chrome.google.com/webstore/detail/stop-load/andkkobbpjnjlenkopioemlapmlc
pbfl

instructions on adding an extension to chromedriver:
http://code.google.com/p/selenium/wiki/ChromeDriver

This is an enhancement?  This should be a bug seeing as setting timeout with 
driver.manage().timeouts().implicitlyWait( is completely ignored in Firefox.  
One would expect this to do what one expects it to do. Run any requests for 
only a specified time , but this is not the case.

When is this going to be fixed???

This is definitely NOT an Enhancement, its a critical Bug.
Please Fix it ASAP.

When pageloadTimeout api is implemented for ChromeDriver, will it fix the 
problem I am facing with .click() hangs when a button click triggers a 
javascript method to open another html dialog/browser window, on which I will 
need to perform some actions such as enter some comment text, then click ok 
button to dismiss this dialog. Currently, since .click() doesn't finish, so the 
script can't perform any action on this dialog, and at the same time, because 
the dialog is not dismissed, the .click() never finishes. When I manually 
dismiss the dialog, that is when I notice .click() completes.

#19, nope, this will not fix that. That is a separate issue; see 
http://code.google.com/p/chromedriver/issues/detail?id=211

For anyone that encounters this problem and is using python, here's my 
monkeypatch to work around the problem.    It uses socket timeouts as amiagkov 
referenced above.  

The biggest caveat here is that we have to kill the chromedriver process on an 
exception because the browser becomes unusable after the timeout is triggered 
(because it keeps waiting for the page to load indefinitely).

https://gist.github.com/timhanus/5592412

Issue 353 has been merged into this issue.

Released in v2.1

Google a lot but not able to get an sample. 

It doesn't work like below. Who can help?

DesiredCapabilities caps = DesiredCapabilities.chrome();
caps.setCapability("webdriver.load.strategy", "unstable");

WebDriver driver = new ChromeDriver(caps);

Issue 23 has been merged into this issue.